No more requirement "be in the release folder" to run cmrel, remove the flag --cloudbuild #43
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.
Not sure what the team thinks, but I figured that it would be worth avoiding the dependency on being in the correct folder in order to run
cmrel
. The cloudbuild files are now embedded into the binary. I thus removed the flag--cloudbuild
.Note to the reviewer:
The downside to this approach is that we can't inspect the
cloudbuild.yaml
file for a givencmrel
version before submitting the build. Should I add a flag--dump-cloudbuild
for bothstage
andpublish
to remediate that?