Skip to content

ci: add the OpenJD release train workflow - #249

Draft
seant-aws wants to merge 5 commits into
OpenJobDescription:mainlinefrom
seant-aws:release-train-caller
Draft

seant-aws wants to merge 5 commits into
OpenJobDescription:mainlinefrom
seant-aws:release-train-caller

Conversation

@seant-aws

@seant-aws seant-aws commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Fixes: N/A (release automation; depends on aws-deadline/.github#130)

What was the problem/requirement? (What/Why)

The OpenJD release train re-releases this repository when an upstream OpenJD package releases: a dependency bump and its tests, in a PR that people review and merge. The train runs in AWS without a GitHub credential, so this repository's own workflow makes its GitHub writes.

What was the solution? (How)

.github/workflows/release_train.yml calls the reusable workflow from aws-deadline/.github#130. It runs on a push to mainline (a merged train PR), when Release: Publish completes (the train job runs only for a successful Publish of this repository's mainline), on workflow_dispatch (an upstream release or a person), daily at 06:17 UTC as a backstop, and Mondays at 15:17 UTC for a planned weekly release check that does nothing yet. After a release here it dispatches the release train of aws-deadline/deadline-cloud-worker-agent. The train opens bot/* PRs for a maintainer to approve, review and merge, then dispatches this repository's own Release: Bump.

dependabot.yml ignores openjd-* and auto_approve.yml never approves an openjd-* update, so Dependabot does not race the train.

What is the impact of this change?

None until an admin sets the variable RELEASE_TRAIN_ENABLED=true; the job is skipped otherwise. It also needs RELEASE_TRAIN_MODE=live (any other value fails the run) and the secret RELEASE_TRAIN_ROLE (the AWS role that may invoke the train's gateway), plus optional RELEASE_TRAIN_DISPATCH_TOKEN and RELEASE_TRAIN_DISPATCH_TOKEN_AWS_DEADLINE (bot-owned, Actions read and write only), which only the dispatch step receives; without them the downstream repositories pick the release up on their daily run. Optional variables: RELEASE_TRAIN_GATEWAY, RELEASE_TRAIN_REGION, RELEASE_TRAIN_WEEKLY. Keep "Allow GitHub Actions to create and approve pull requests" on, and exclude refs/heads/bot/** from the branch-creation rulesets.

How was this change tested?

actionlint and zizmor (--no-config) are clean. The same caller, pointed at fork branches, ran a release end to end on forks, including the downstream dispatch.

  • Have you run the tests? Not applicable: workflow and Dependabot configuration only.

Was this change documented?

Yes, in the workflow's header comment.

  • Are relevant docstrings in the code base updated? Not applicable.

Is this a breaking change?

No.

Does this change impact security?

The job gets contents, pull-requests and actions write and id-token: write, used only by the reusable workflow's checked actions (bot/* branches only; no repository code is checked out or run). The AWS role trusts only this repository's mainline subject, so a pull_request run can never assume it.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The caller of aws-deadline/.github's reusable release-train workflow, inert until the RELEASE_TRAIN_ENABLED variable is true. Dependabot no longer proposes openjd-* updates and the auto-approve job skips them: the release train owns those bumps.

Signed-off-by: Sean Tang <171081544+seant-aws@users.noreply.github.com>
…rganization

Pass RELEASE_TRAIN_DISPATCH_TOKEN (OpenJobDescription repositories) and RELEASE_TRAIN_DISPATCH_TOKEN_AWS_DEADLINE (aws-deadline repositories) to the reusable workflow's per-organization dispatch secrets, in place of the release workflows' token. Both are optional; without one, that organization's downstream repositories pick a release up on their daily run.

Signed-off-by: Sean Tang <171081544+seant-aws@users.noreply.github.com>
@github-actions

github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Claude review · advisory

Reviewed 812cb1c (changes since c726215): 0 new, 0 resolved.

Open: 0 blocking · 0 should-fix · 0 nit. ✅ Nothing blocking.

Fix or reply to each thread; the next revision's review re-checks open threads and resolves those it agrees are handled. Resolving a thread yourself also closes it. Later revisions review only what changed.

Runs the release train every Monday next to its daily backstop, for the train's planned weekly release check. It does nothing until the release train's weekly mode is enabled; the repository variable RELEASE_TRAIN_WEEKLY=false pauses it.

Signed-off-by: Sean Tang <171081544+seant-aws@users.noreply.github.com>
The Dependabot comment said the train writes release notes, and the contents: write comment said it creates tags and releases. The train opens PRs that people review and merge; release notes come from this repository's own generator, and Release: Publish tags and releases (the train makes a prerelease tag only in rehearsal mode). The workflow_run comment now says what the reusable workflow reads of the triggering run and that it goes on only for a successful Publish of the release branch.

Signed-off-by: Sean Tang <171081544+seant-aws@users.noreply.github.com>
The reusable workflow no longer has a rehearsal mode or creates tags, so the permission comments and the mode note now say what the train does: push bot/* branches, dispatch Release: Bump, and run only with RELEASE_TRAIN_MODE=live.

Signed-off-by: Sean Tang <171081544+seant-aws@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant