Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions Jenkinsfile
Original file line number Diff line number Diff line change
Expand Up @@ -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'],
])
2 changes: 0 additions & 2 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down