build on all dev branches, build on any branch named starting with "pr/" #1378
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
beckjake
force-pushed
the
ci/add-build-tag
branch
from
1aa049f
to
161a78d
Compare
beckjake
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the azure pipelines CI process a bit. Instead of only running on changes to
master, it will now run on any changes to:masterdev/pr/The latter should help with contributor PR testing, though it's kind of hacky: Basically, do all the things you'd do to trigger circleci builds, except make sure you've named your branch starting with "pr/".
I don't think this is the most elegant solution possible, and we'll want to prune our branches, but it's something.