-
Notifications
You must be signed in to change notification settings - Fork 212
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
fix: set pipeline variables even if build fails #5110
Merged
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
zachary-bailey
requested review from
juan-lee,
cameronmeissner,
UtheMan,
ganeshkumarashok,
anujmaheshwari1,
AlisonB319,
Devinwong,
lilypan26,
ShiqianTao,
AbelHu,
junjiezhang1997,
jason1028kr,
djsly,
phealy,
r2k1 and
timmy-wright
as code owners
October 17, 2024 15:12
djsly
approved these changes
Oct 17, 2024
cameronmeissner
approved these changes
Oct 17, 2024
zachary-bailey
force-pushed
the
zb/alwaysRunSetPipelineVariablesStep
branch
from
October 17, 2024 17:42
05ad779
to
3d481b6
Compare
zachary-bailey
force-pushed
the
zb/alwaysRunSetPipelineVariablesStep
branch
from
October 17, 2024 21:40
3d481b6
to
5f18635
Compare
zachary-bailey
force-pushed
the
zb/alwaysRunSetPipelineVariablesStep
branch
from
October 18, 2024 14:21
5f18635
to
db60107
Compare
zachary-bailey
force-pushed
the
zb/alwaysRunSetPipelineVariablesStep
branch
from
October 21, 2024 14:26
db60107
to
18f1210
Compare
zachary-bailey
force-pushed
the
zb/alwaysRunSetPipelineVariablesStep
branch
from
October 21, 2024 18:07
18f1210
to
bf34424
Compare
zachary-bailey
force-pushed
the
zb/alwaysRunSetPipelineVariablesStep
branch
from
October 22, 2024 14:35
bf34424
to
080333c
Compare
zachary-bailey
force-pushed
the
zb/alwaysRunSetPipelineVariablesStep
branch
from
October 23, 2024 19:17
080333c
to
5173e6c
Compare
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 type of PR is this?
/kind bug
What this PR does / why we need it:
This PR changes the logic in our pipeline template to always run the
Set Pipeline Variables
step, even if the build fails. This helps ensure thatcleanup.sh
will always be run if the packer build actually started and povisioned resources.Which issue(s) this PR fixes:
Set Pipeline Variables
would not run if the build failed.Requirements: