Merge pull request #1249 from MarkEWaite/test-java-17

Test with Java 17 in addition to Java 11 and Java 8

Author: MarkEWaite

Jenkinsfile

@@ -2,6 +2,7 @@
 
 buildPlugin(failFast: false,
             configurations: [
-                [platform: 'linux', jdk: '11'],
-                [platform: 'windows', jdk: '8'],
+                [platform: 'linux',   jdk: '17', jenkins: '2.342'],
+                [platform: 'linux',   jdk: '11'],
+                [platform: 'windows', jdk:  '8'],
             ])

pom.xml

@@ -61,8 +61,6 @@
     <revision>4.11.1</revision>
     <changelist>-SNAPSHOT</changelist>
     <gitHubRepo>jenkinsci/${project.artifactId}-plugin</gitHubRepo>
-    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-    <argLine>-Dfile.encoding=${project.build.sourceEncoding}</argLine>
     <jenkins.version>2.289.1</jenkins.version>
     <no-test-jar>false</no-test-jar>
     <useBeta>true</useBeta>

src/main/java/hudson/plugins/git/extensions/GitSCMExtension.java

@@ -104,7 +104,7 @@ public FilePath getWorkingDirectory(GitSCM scm, AbstractProject<?, ?> context, F
      * the chosen revision and returning it) or manipulate the state of the working tree (such as
      * running git-clean.)
      *
-     * <h3>{@link #decorateRevisionToBuild(GitSCM, Run, GitClient, TaskListener, Revision, Revision)} vs {@link BuildChooser}</h3>
+     * <strong>{@link #decorateRevisionToBuild(GitSCM, Run, GitClient, TaskListener, Revision, Revision)} vs {@link BuildChooser}</strong>
      * <p>
      * {@link BuildChooser} and this method are similar in the sense that they both participate in the process
      * of determining what commits to build. So when a plugin wants to control the commit to be built, you have