[Tooling] Introduce pipelines to trigger release tasks on CI #2720
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
It's already called during `publish_release` lane later, which is a better time for it to be called rather than as early as `finalize_release`. See Automattic/apps-infra-plans#83
AliSoftware
added
the
[Type] Tooling
AliSoftware
requested review from
SergioEstevao and
a team
and removed request for
a team
iangmaia
reviewed
Jan 31, 2025
| retry: | ||
| manual: | ||
| allowed: false | ||
| reason: "If this job fails, please trigger a new build from ReleasesV2 instead of retrying this step" |
There was a problem hiding this comment.
Suggested change
| reason: "If this job fails, please trigger a new build from ReleasesV2 instead of retrying this step" | |
| reason: "If this job fails, please trigger a new build from ReleasesV2 instead of retrying this step" |
There was a problem hiding this comment.
Not sure if this 👆 works, but I just wanted to highlight the lack of line break at the end 😅
There was a problem hiding this comment.
Lol I asked Cursor to add all missing newlines at EOF… which it did in 1ef0c15 but it seems it missed some… should have double-checked its work…
There was a problem hiding this comment.
Fixed in c74eda6
iangmaia
reviewed
Jan 31, 2025
| retry: | ||
| manual: | ||
| allowed: false | ||
| reason: "If this job fails, please trigger a new build from ReleasesV2 instead of retrying this step" |
There was a problem hiding this comment.
Suggested change
| reason: "If this job fails, please trigger a new build from ReleasesV2 instead of retrying this step" | |
| reason: "If this job fails, please trigger a new build from ReleasesV2 instead of retrying this step" |
AliSoftware
force-pushed
the
tooling/release-on-ci
branch
from
1ef0c15 to
c74eda6
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.
This is a mirroring of the similar changes that were recently introduced in PCAndroid.
Description
As part of this Project Thread: paaHJt-78B-p2, this introduces
.buildkite/release-pipelines/*.ymlfiles that will take care of callingfastlane code_freezeand similar lanes called during the release process.Those lanes are currently called by the Release Manager on their own Mac, so the point of introducing those pipelines is to be able to instead switch to make those kicker lanes be run on CI instead.
Created pipelines
List of
.buildkite/release-pipelines/*.ymlfiles calling their associatedfastlanelane during ReleaseV2 scenario:code_freezenew_beta_releasefinalize_releasepublish_releasenew_hotfix_releasefinalize_hotfix_releaseScenario steps update in ReleasesV2
Once this lands, we will be able to also land the companion PR in wpcom to update the Release Scenario in MC (Internal Ref: 171892-ghe-Automattic/wpcom) to replace the currently-manual tasks like "Call
bundle exec fastlane code_freeze" and the likes with automated tasks instead—i.e. tasks that will present a clickable button on ReleasesV2 which, when clicked, will trigger those lanes on CI—thus not requiring Release Managers to run those from their personal Macs anymore.Testing Instructions
The only way to test this is during the next release process that will adopt those changes (hopefully during
7.82)