Skip to content

Test Jenkins 2.545 incremental#6179

Closed
MarkEWaite wants to merge 1 commit intojenkinsci:masterfrom
MarkEWaite:test-2.545-incremental
Closed

Test Jenkins 2.545 incremental#6179
MarkEWaite wants to merge 1 commit intojenkinsci:masterfrom
MarkEWaite:test-2.545-incremental

Conversation

@MarkEWaite
Copy link
Contributor

@MarkEWaite MarkEWaite commented Jan 4, 2026

Test Jenkins 2.545 incremental

Do not merge

Built from Jenkins core pull request:

Includes pull requests that are currently marked as "Ready for merge":

Reverts pull requests:

Testing done

Confirmed that git-client passes InjectedTest without the two reverted pull requests and confirmed that it fails the InjectedTest with the two reverted pull requests.

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant pull requests, esp. upstream and downstream changes

@MarkEWaite
Copy link
Contributor Author

Closing after confirming that tests pass.

@MarkEWaite MarkEWaite closed this Jan 4, 2026
@MarkEWaite MarkEWaite deleted the test-2.545-incremental branch January 4, 2026 02:13
@MarkEWaite
Copy link
Contributor Author

@uhafner and @NotMyFault are other changes needed to the plugin bill of materials in order to accept the Jenkins core change to require Java 21?

When I include the two reverted pull requests, the tests fail locally. I tested locally with the command:

LINE=weekly PLUGINS=git-client TEST=InjectedTest bash ./local-test.sh

@NotMyFault
Copy link
Member

@uhafner and @NotMyFault are other changes needed to the plugin bill of materials in order to accept the Jenkins core change to require Java 21?

When I include the two reverted pull requests, the tests fail locally. I tested locally with the command:

LINE=weekly PLUGINS=git-client TEST=InjectedTest bash ./local-test.sh

#6180 will be needed as well, given we cannot run on Java 17 anymore.

@MarkEWaite
Copy link
Contributor Author

I found the issue. The lib-version-number does not recognize the Java 25 class file version number. It also does not recognize the Java 21 class file version number. Pull request coming soon. Will need a new version of that library and a new version of the Maven hpi plugin that includes the new version of the library

MarkEWaite added a commit to MarkEWaite/lib-version-number that referenced this pull request Jan 4, 2026
Allow a Java specification version to be converted to a Java class version.

Fixes issue detected in plugin BOM pull request:

* jenkinsci/bom#6179
@MarkEWaite
Copy link
Contributor Author

MarkEWaite commented Jan 4, 2026

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