This repository was archived by the owner on Sep 30, 2024. It is now read-only.
fix(sg): cloud ephemeral - do no trigger builds on main-dry-run#64190
Merged
Conversation
jhchabran
approved these changes
Jul 31, 2024
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Triggering cloud ephemeral builds on main-dry-run leads to unexpected results which is due to how the eventual pipeline is generated.
Closes DINF-165
Generated pipeline?
The pipeline gets generated based on what matches first. We detect cloud ephemeral builds if there is an environment variable
CLOUD_EPHEMERAL=true. We detect main-dry-runs if the branch prefix ismain-dry-run...Now due to the
main-dry-runmatch happening before the cloud ephemeral match a Cloud Ephemeral build on a main dry run gets detected as just amain-dry-runbuild.Alternatives
Sure we can just move the Cloud Ephemeral match earlier, but it's difficult to say what else might break. We could also just add the we force the runtype to always be
CloudEphemeralif we're on the Cloud Ephemeral pipeline, but I don't want to make the pipline a special snowflake and detect the current pipeline just for Cloud Ephemeral.Why deny it the deployment?
Ultimately,
main-dry-runbuilds are meant for ...mainnot cloud ephemeral. People can just switch to their original branch and runsg cloud eph deployand the branch will be deployed with no issueTest plan
Executed locally
Changelog
main-dry-runbranches on Cloud Ephemeral.