-
Notifications
You must be signed in to change notification settings - Fork 285
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
Run buildkite_pipeline_upload
on branch HEAD
#1673
Run buildkite_pipeline_upload
on branch HEAD
#1673
Conversation
Generated by 🚫 Danger |
# not the commit that triggered the automation that eventaully called this. | ||
# | ||
# Useful during release automation builds that make additional commits to the release branch. | ||
{ **environment, BUILDKITE_COMMIT: last_git_commit[:commit_hash] } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not the most elegant solution... One alternative could be to force the release script to checkout release branch, but that seem like limiting the script?
📲 You can test the changes from this Pull Request in Simplenote Prototype Build by scanning the QR code below to install the corresponding build.
|
The build I triggered to test this was green, but it was a false positive 😞 The upload to TestFlight succeeded but that's because it uploaded version 4.55.0.1 which originally failed. What it should have uploaded was 4.55.0.2 The logs show the But when the uploaded steps run, the commit the have in their environment is the original one: I guess we have to force checkout the latest release branch from the script after all. |
See inline comments.
This is an attempt to solve the failure seen in https://buildkite.com/automattic/simplenote-ios/builds/1194 where the injected beta build steps run on the commit that triggered the injecting build, not the commit in which the codebase was when the steps were injected.