-
Notifications
You must be signed in to change notification settings - Fork 181
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Let's see if this creates the build-config on ci.jenkins.io
- Loading branch information
Showing
1 changed file
with
6 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
#!/usr/bin/env groovy | ||
|
||
/* `buildPlugin` step provided by: https://github.com/jenkins-infra/pipeline-library */ | ||
buildPlugin() // jenkinsVersions: [null, '2.107.2'], platforms: ['linux'] | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong. |
||
|
||
// More complex Jenkinsfile sample: https://github.com/jenkinsci/graphql-server-plugin/blob/master/Jenkinsfile |
If you want to test for JDK 8 & 11 (as in the Travis CI setup) I suggest to use one if these
a)
buildPlugin(configurations: buildPlugin.recommendedConfigurations())
b)
buildPlugin(jdkVersions: [8, 11])
This change should be performed by the repository owner as ci.jenkins.io is set up the way that changes in Jenkinsfiles are only trusted by developers with write access to the repository. Therefore if I would create a pull request it would still run with the previous version of the Jenkinsfile and only use the version when it's merged to the master branch.