Combine all release jobs into one stage #436
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
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.
Currently publishing to the supported target feeds is split up into stages that sequentially depend on each other.
If one of the stages fail, then all consequent stages will not run.
It creates some unexpected issues like with the release 0.9.7 where the failure to publish duplicated NuGet package to the ADO feed prevented publishing to other feeds.
This PR replaces all the stages with one stage while keeping the same jobs per each target feed.
After the change all the jobs can be run in parallel and failure in one job does not prevent other jobs from completion.
It also gives us an opportunity to rerun only failed jobs in case if we just need to update API key or change any other settings outside of the pipeline.