Trigger adjacent jobs in release process#1870
Merged
elliotmjackson merged 7 commits intomainfrom Feb 28, 2023
Merged
Conversation
joshcarp
approved these changes
Feb 28, 2023
Contributor
Author
paul-sachs
reviewed
Feb 28, 2023
Co-authored-by: Paul Sachs <11449728+paul-sachs@users.noreply.github.com>
paul-sachs
approved these changes
Feb 28, 2023
twoism
pushed a commit
that referenced
this pull request
Mar 2, 2023
We had chained a number of jobs meaning that if one failed, they all failed. This PR changes that behaviour by having the following steps depend on post-release and then run independently. - trigger npm publish - trigger homebrew-buf release - trigger vim-buf release - trigger docs.buf.build release - trigger buf-setup-action release i achieved this by posting the `VERSION` as an output of the `post-release` job like [this](https://docs.github.com/en/actions/using-jobs/defining-outputs-for-jobs) --------- Co-authored-by: Paul Sachs <11449728+paul-sachs@users.noreply.github.com>
Monirul1
pushed a commit
to Monirul1/buf
that referenced
this pull request
Apr 30, 2023
We had chained a number of jobs meaning that if one failed, they all failed. This PR changes that behaviour by having the following steps depend on post-release and then run independently. - trigger npm publish - trigger homebrew-buf release - trigger vim-buf release - trigger docs.buf.build release - trigger buf-setup-action release i achieved this by posting the `VERSION` as an output of the `post-release` job like [this](https://docs.github.com/en/actions/using-jobs/defining-outputs-for-jobs) --------- Co-authored-by: Paul Sachs <11449728+paul-sachs@users.noreply.github.com>
This file contains hidden or 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
3 participants
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.
We had chained a number of jobs meaning that if one failed, they all failed. This PR changes that behaviour by having the following steps depend on post-release and then run independently.
i achieved this by posting the
VERSIONas an output of thepost-releasejob like this