Repository navigation
Enable continuous delivery - #344
Merged
Merged
Conversation
Adds the jenkins-infra CD workflow (manual dispatch only, no check_run auto-trigger), switches the POM to CD versioning with a manual '1.' prefix (releases will be 1.<commit-depth>.v<hash>, e.g. 1.653.v4eb30b9fc033), and removes the now-redundant release-drafter config and workflow per https://www.jenkins.io/doc/developer/publishing/releasing-cd/
h3nr1-d14z
force-pushed
the
enable-cd
branch
from
September 10, 2026 18:19
d34cbe1 to
57780c1
Compare
Contributor
|
You don't need to maintain |
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 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.
Follows https://www.jenkins.io/doc/developer/publishing/releasing-cd/ — increments are already enabled, so this is the rest of the checklist:
.github/workflows/cd.yamlfrom the jenkins-infra template, with thecheck_runtrigger removed so releases happen only on manual dispatch1.prefix:<revision>1</revision>+${revision}.${changelist}, so releases will look like1.653.v4eb30b9fc033instead of jumping to a bare triple-digit major (current depth is 653, comfortably above the last release 1.25 and the pending 1.26)Two notes for reviewers:
MAVEN_USERNAME/MAVEN_TOKENrepo secrets are referenced by the workflow and not yet configured; I'll add them once this is approved (Artifactory API key).mvn release:prepare release:performof 1.26 is in flight to ship the fix: surface DNS and connection errors instead of fake 404/408 responses #343 fix under the current versioning, so this should merge after that release is out.Also worth confirming whether the release-drafter GitHub App (as opposed to the workflow) is installed on this repo — if it is, it should be removed per the doc; I can't see App installations from here.