Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger finish release pipeline as post_commit action of promotion to current #7164

merged 2 commits into from Nov 8, 2019


Copy link

smacfarlane commented Nov 6, 2019

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

Signed-off-by: Scott Macfarlane

… current

Signed-off-by: Scott Macfarlane <>
Signed-off-by: Scott Macfarlane <>
@smacfarlane smacfarlane merged commit 6479135 into master Nov 8, 2019
5 checks passed
5 checks passed
DCO This commit has a DCO Signed-off-by
buildkite/habitat-sh-habitat-master-verify Build #4132 passed (25 minutes, 54 seconds)
buildkite/habitat-sh-habitat-master-website Build #1211 passed (56 seconds)
continuous-integration/travis-ci/pr The Travis CI build passed
expeditor/config-validation Validated your Expeditor config file
@chef-expeditor chef-expeditor bot deleted the sm/connect_finish_release_pipeline branch Nov 8, 2019
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
None yet
2 participants
You can’t perform that action at this time.