Split release pipeline into stages #727
Merged
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
|
/azp run porter-release |
|
Azure Pipelines successfully started running 1 pipeline(s). |
carolynvs
force-pushed
the
release-pipes
branch
3 times, most recently
from
6376e09 to
a317726
Compare
carolynvs
force-pushed
the
release-pipes
branch
from
a317726 to
f900bae
Compare
|
You can see what the release build looks like here: https://dev.azure.com/deislabs/porter/_build/results?buildId=3765 Once this is merged, then I can turn on being able to trigger it safely to test it in a PR. It brought the build down to ~23min. |
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.
What does this change
Splits up the release pipeline into stages.
What issue does it fix
Closes #673
Notes for the reviewer
🏎
Checklist