question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Remote testing branches

See original GitHub issue

Currently we are running Sauce Labs on pushes to all branches. PRs are not included as of #390.

That is OK and working fine for PRs and pushes to master.

After checking the Greenkeeper behavior, I noticed that it pushes it’s changes to a newly created local branch and then it creates a PR to master.

The problem is that it ends up starting two Travis jobs, one using Sauce Labs (push to branch) and one using local Chrome (PR). Since Sauce Labs connection can be flakey, it may not be ideal to use it to check dependency updates or even simple branch experiments.

I believe that we should only keep Sauce on for pushes to the master branch.

This seems right because the widget on README is related to master as well.

The question now is: how do we want to handle beta? Should we test it on Sauce Labs too or wait until it arrives on master?

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
mkxmlcommented, Dec 1, 2016

OK, created branch remote-testing to test the new behavior.

Works fine so far (only Chrome running): https://travis-ci.org/developit/preact/builds/180537936

Now let’s do a PR to master to complete walking through @greenkeeperio-bot’s steps.

0reactions
developitcommented, Dec 2, 2016

Yay! 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

Remote Branches - Git
Remote branches are references (pointers) to the state of branches in your remote repositories. They're local branches that you can't move; they're moved ......
Read more >
Remote Testing - Public Safety Testing
Public Safety Testing is pleased to offer Candidates the ability to take their written exams in locations around the United States, scheduled on...
Read more >
How to Checkout a Remote Branch in Git - W3docs
Checking out Branches. And, finally, to checkout a branch in multiple remotes, you should use the following command: git checkout -b test <name...
Read more >
Git Checkout Remote Branch: Code Examples, Tutorials & More
Git is one of the most useful tools for developers and development teams. And Git checkout remote branch makes it easier for collaboration....
Read more >
Dev local test remote by github and arc | by marswriter - Medium
This doc is discussing a git based solution. The key idea is to push local code into github non-master branch, then the remote...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found