Build With Parameters

Allows the user to provide parameters for a build in the url, prompting for confirmation before triggering the job.

The plugin exposes $JENKINS/job/$JOB/parambuild url to trigger the build with parameter. Unlike $JENKINS/job/$JOB/buildWithParameters, a human must confirm that the parameters are correct before the build is triggered. This is useful if you want to create a list of jobs with parameters to trigger ahead of time, and execute it at some future date (e.g. a deployment plan).

An example triggering of a job with the plugin:

String parameters can be trimmed using Jenkins' built-in per-parameter trim option. Enable it in the string parameter's configuration, or set trim: true in a Pipeline parameter declaration:

string(name: 'MY_PARAM', defaultValue: '', trim: true)

The setting applies when the parameter value is created, including when submitting the /parambuild form. Parameters without trimming enabled retain their whitespace.

By default, /parambuild allows blank string parameter values. Add allowBlankStrings=false to the URL to reject string or text parameters whose submitted value (or configured default when no value is submitted) is empty or whitespace-only before scheduling the build. The setting applies to all string and text parameters on that submission; other parameter types are unchanged.

For example:

/job/my-job/parambuild?BRANCH=main&allowBlankStrings=false

Run mvn test to execute the tests, or mvn package to build the plugin HPI in target/. Run mvn hpi:run to start a development Jenkins with the plugin installed.

See CONTRIBUTING.md for the development workflow.

The latest releases are documented in the GitHub releases page.

• Add regression coverage for custom parameter rendering, including Parameter Separator (#65).

• Add an allowBlankStrings URL option to reject blank string values on /parambuild submissions (#63).
• Document Jenkins' built-in option for trimming string parameters (#61).
• Add coverage for parameter handling and form security checks (#84).
• Fix file parameters so files selected on the confirmation form are passed to the build (#36).

• Validate submissions containing a single custom parameter (#83).

• Support custom parameter types on the confirmation form (#82).

• Honor the configured markup formatter for parameter descriptions (#81).
• Add contributor and architecture documentation (#80).

• Skip null parameter values when scheduling builds (#79).
• Enable Jenkins Security Scan, migrate tests to JUnit Jupiter, and update build dependencies.

• Migrate from EE 8 to EE 9 and update the Jenkins baseline to 2.440.3.
• Update test dependencies, parallelize tests, and test with Java 25.

• Fix parameter evaluation order (#23).
• Update the Jenkins LTS version and modernize the code.

• Replace JSR 305 annotations and enable continuous delivery and incremental versioning.

• Update to support icons removal from Jenkins Core
• Bumped parent POM and minimal Jenkins version are now 2.204

• Move documentation to GitHub

• Fix XSS vulnerability as reported in security advisory.
• Fix CSRF vulnerability as reported in security advisory.

• Require Jenkins 2.60.3 or newer.

• Fixed 404 error for not logged user (JENKINS-25534).

• Support for pipelines (JENKINS-35378).

• Hide job action from UI to avoid confusion (JENKINS-25413).