Add Jenkinsfile to build plugin on the Jenkins Infrastructure #86
Conversation
This file contains hidden or 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
gounthar
force-pushed
the
plugin-modernizer/setupjenkinsfile
branch
2 times, most recently
from
df05419 to
9c12984
Compare
gounthar
changed the title
gounthar
force-pushed
the
plugin-modernizer/setupjenkinsfile
branch
from
9c12984 to
da08477
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello
browserstack-integrationdevelopers! 👋This is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:
Setup the Jenkinsfile
io.jenkins.tools.pluginmodernizer.SetupJenkinsfile
Why is this important?
This pull request ensure your plugin is build on the Jenkins infrastructure.
Based on your plugin requirements, the Jenkins infrastructure will build your plugin using Java 8 and 11.
There will come a time when we no longer support plugins built with JDK 8 or 11.
After this PR is merged, we will submit additional automated PRs to enable your plugin to build with Java 17 and 21.