Patch Parameter Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID patch-parameter Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
1.2 (archives)
Jul 08, 2014
Source Code
Issue Tracking
Pull Requests
Open Issues
Pull Requests
n/a (id: kohsuke)
Usage Installations 2014-Nov 457
2014-Dec 476
2015-Jan 485
2015-Feb 501
2015-Mar 531
2015-Apr 563
2015-May 565
2015-Jun 582
2015-Jul 585
2015-Aug 599
2015-Sep 664
2015-Oct 679

This plugin adds a new parameter type to a parameterized build, where the user can optionally submit a patch file. This patch file will be then applied to the workspace before the build commences.


This plugin is developed to enable server-side testing of a change that's not yet committed (also known as pre-tested commit). In this workflow, a developer works on a change locally, and before he checks in the changes, he'd take the diff, submit it to Jenkins, and verify that it builds OK. Once the patch is verified by Jenkins, the user will then actually commit the change.

This can be also useful for situations where a proper test environment is tricky to replicate locally, or where your Jenkins can run tests considerably faster than developers' local computers.

Note that on distributed version control systems, there's often a better way to do this. See Gerrit Trigger or Subversion Merge Plugin or validated merge feature from CloudBees.


In the job configuration screen, click "This build is parameterized", then add "patch as a parameter".


Version 1.2 (Jul 8, 2014)

  • Fixed the handling of patch produced by Mercurial (pull request)

Version 1.1 (Aug 16, 2013)

  • Small change to make it more clear why a patch failed to apply

    Version 1.0 (Oct 7, 2012)

  • Initial release
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment