Skip to content

Bump Jenkins baseline to 2.479.3 and update the plugin BOM - #287

Merged
ogulcanaydogan merged 1 commit into
jenkinsci:masterfrom
ogulcanaydogan:chore/bump-jenkins-baseline-for-bom
Jul 23, 2026
Merged

Bump Jenkins baseline to 2.479.3 and update the plugin BOM#287
ogulcanaydogan merged 1 commit into
jenkinsci:masterfrom
ogulcanaydogan:chore/bump-jenkins-baseline-for-bom

Conversation

@ogulcanaydogan

Copy link
Copy Markdown
Contributor

The bom-2.479.x update to 5054.v620b_5d2b_d5e6 pulls in pipeline-stage-tags-metadata 2.2255, which requires Jenkins 2.479.3 or higher. The Dependabot bump in #170 only raised the BOM, so it failed to build with:

Dependency org.jenkinsci.plugins:pipeline-stage-tags-metadata:jar:2.2255.v56a_15e805f12 requires Jenkins 2.479.3 or higher.

This raises the baseline to 2.479.3 alongside the BOM update so the build passes. Supersedes #170.

Testing

mvn clean test-compile passes against the updated BOM.

The bom-2.479.x update to 5054.v620b_5d2b_d5e6 pulls in
pipeline-stage-tags-metadata 2.2255, which requires Jenkins 2.479.3 or
higher, so the baseline is raised to match. Supersedes jenkinsci#170, which
bumped only the BOM and could not build.

Signed-off-by: Ogulcan Aydogan <[email protected]>
@ogulcanaydogan
ogulcanaydogan force-pushed the chore/bump-jenkins-baseline-for-bom branch from e32c1b6 to 98ee20d Compare July 23, 2026 11:01
Comment thread pom.xml
<gitHubRepo>jenkinsci/${project.artifactId}-plugin</gitHubRepo>
<jenkins.baseline>2.479</jenkins.baseline>
<jenkins.version>${jenkins.baseline}.1</jenkins.version>
<jenkins.version>${jenkins.baseline}.3</jenkins.version>

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ogulcanaydogan
ogulcanaydogan merged commit 5a8a675 into jenkinsci:master Jul 23, 2026
18 checks passed
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.

2 participants