Trigger finish release pipeline as post_commit action of promotion to current #7164
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
… current Signed-off-by: Scott Macfarlane <smacfarlane@chef.io>
Signed-off-by: Scott Macfarlane <smacfarlane@chef.io>
scotthain
approved these changes
Nov 8, 2019
smacfarlane
added
Expeditor: Skip Version Bump
and removed
Expeditor: Skip Version Bump
labels
chef-expeditor bot
pushed a commit
that referenced
this pull request
Nov 8, 2019
Obvious fix; these changes are the result of automation not creative thinking.
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.
When a set of artifacts is promoted to current, there are a number of actions that need to be taken. This wires up our pipeline to start as a post_commit action on the promotion from current. This pipeline should not start until after the promotion is finished, and only if it succeeds.
@tduffield Is this the correct pattern for what I'm trying to accomplish when the pipelines exist in the same repo, or should it subscribe to a workload completed like we did in https://github.com/habitat-sh/homebrew-habitat/blob/master/.expeditor/config.yml#L9
Signed-off-by: Scott Macfarlane smacfarlane@chef.io