Skip to content

Require Java 11 and Jenkins 2.361.4 or newer - #1367

Merged
MarkEWaite merged 8 commits into
jenkinsci:masterfrom
MarkEWaite:require-java-11
Dec 25, 2022
Merged

Require Java 11 and Jenkins 2.361.4 or newer#1367
MarkEWaite merged 8 commits into
jenkinsci:masterfrom
MarkEWaite:require-java-11

Conversation

@MarkEWaite

@MarkEWaite MarkEWaite commented Dec 3, 2022

Copy link
Copy Markdown
Contributor

Require Java 11 and Jenkins 2.361.4 or newer

  • Link to Java 11 javadoc, not Java 8
  • CI test with Java 11 and Java 17
  • Use the simpler documentation URL
  • Remove unused properties, document required properties
  • Require Jenkins 2.361.4 or newer
  • Remove unused import
  • Use git client plugin 4.0 incremental

Prepare for git plugin 5.0.0 release with requirement for Java 11 and with additional changes for the addition of Pipeline symbols to make Pipelines easier to express.

Checklist

  • I have read the CONTRIBUTING doc
  • I have referenced the Jira issue related to my changes in one or more commit messages
  • I have added tests that verify my changes
  • Unit tests pass locally with my changes
  • I have added documentation as necessary
  • No Javadoc warnings were introduced with my changes
  • No spotbugs warnings were introduced with my changes
  • Documentation in README has been updated as necessary
  • Online help has been added and reviewed for any new or modified fields
  • I have interactively tested my changes
  • Any dependent changes have been merged and published in upstream modules (like git-client-plugin)

Types of changes

  • New feature (non-breaking change which adds functionality)

Further comments

Needs additional testing in:

  • Plugin compatibility tester in the Jenkins bill of materials
  • Interactive testing in Mark Waite's multi-platform cluster
  • Interactive testing by other users

Once this pull request is merged, then the add-symbols branch needs to be merged (probably after a squash or a rebase to make the history less filled with debris). The "add symbols" change is the reason for the increment of the major version from 4.x to 5.x.

I hope that there is no incompatibility created by the "add symbols" change. I've tested deeply and widely for compatibility in the "add symbols" change. The test automation of the "add symbols" change attempts to verify many different scenarios continue to work after the change. However, it is a large enough change that I believe it justifies incrementing the major version.

@MarkEWaite MarkEWaite added the enhancement Improvement or new feature label Dec 3, 2022
@github-actions github-actions Bot added dependencies Dependency related change documentation Improvements or additions to documentation test labels Dec 3, 2022
@MarkEWaite MarkEWaite removed dependencies Dependency related change documentation Improvements or additions to documentation test labels Dec 3, 2022
@github-actions github-actions Bot added dependencies Dependency related change documentation Improvements or additions to documentation test labels Dec 4, 2022
Comment thread pom.xml Outdated
Comment thread pom.xml Outdated
<dependency>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>git-client</artifactId>
<version>4.0.0-rc3300.80c23f8e08ec</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.

FWIW I like to add such things to dependencyManagement with a TODO comment to delete once bom picks it up.

@basil basil left a comment

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.

jenkinsci/git-client-plugin#939 and this PR work fine for me on my local Linux development machine with both Freestyle and Pipeline jobs cloning with both command-line Git and JGit on the latest weekly release and Java 19.

MarkEWaite added a commit to MarkEWaite/pipeline-groovy-lib-plugin that referenced this pull request Dec 18, 2022
Git plugin 5.0 will require Java 11 and will add symbols to improve
the Pipeline syntax editing experience.  The test being modified in
this pull request checks the specific syntax of the Pipeline snippet
syntax generator.  Adapt the test to check for current syntax with git
plugin 4.x releases and for new syntax with any other releases.

jenkinsci/git-client-plugin#939 is the git
client plugin pull request that prepares git client plugin 4.0.0.
It will require Java 11 and will upgrade from JGit 5.13.1 to JGit 6.4.0.

jenkinsci/bom#1619 is the bom draft pull request
that confirms git client plugin 4.0.0 pre-release works in the plugin bom.

jenkinsci/git-plugin#1367 is the git plugin pull
request that prepares git plugin 5.0.0.  It will require Java 11.

jenkinsci/bom#1624 is the bom draft pull request
that tests git plugin 5.0.0 works in the plugin bom.

jenkinsci/git-plugin#1373 is the git plugin pull
request that relies on jenkinsci/git-plugin#1367
and adds symbols to the git plugin.

jenkinsci/bom#1625 is the bom draft pull request
that tests git plugin 5.0.0 with added symbols works in the plugin bom.
It detected this test failure when run with git plugin 5.0.0 pre-release.
@github-actions github-actions Bot removed the test label Dec 25, 2022
@MarkEWaite MarkEWaite removed dependencies Dependency related change documentation Improvements or additions to documentation labels Dec 25, 2022
@MarkEWaite
MarkEWaite enabled auto-merge (rebase) December 25, 2022 17:44
@MarkEWaite
MarkEWaite merged commit ae196bf into jenkinsci:master Dec 25, 2022
@MarkEWaite
MarkEWaite deleted the require-java-11 branch December 25, 2022 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Improvement or new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants