Update Jenkins version

Require a newer minimum Jenkins version

Jenkins plugins declare a minimum supported Jenkins version. The minimum Jenkins version is a good way for plugin developers to indicate the range of Jenkins versions they are willing to support and test. See the developer documentation for the recommended minimum Jenkins version.

Create a branch

Create a git branch for your local work with the command:

$ git checkout -b require-newer-core master

Update minimum required Jenkins version

Update the minimum required Jenkins version by setting a jenkins.version value in the properties section of the pom.xml file:


If the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version. The git diff might look like this:

-        <artifactId>bom-2.319.x</artifactId>
+        <artifactId>bom-2.346.x</artifactId>

Create a pull request

Commit that change:

$ git add pom.xml
$ git commit -m "Require 2.346.3 as minimum Jenkins version"

Push the change to GitHub:

$ git push origin --set-upstream require-newer-core
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
remote: Create a pull request for 'require-newer-core' on GitHub by visiting:
remote: https://github.com/user/your-plugin/pull/new/require-newer-core
To github.com:user/your-plugin.git
 * [new branch]      require-newer-core -> require-newer-core
Branch 'require-newer-core' tracking remote branch 'require-newer-core'.

Notice that the output of the command includes the URL, which can be used to open a pull request. Copy that URL in your web browser and submit a pull request.