Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Pipeline: Input Step on the plugin site for more information.

Older versions of this plugin may not be safe to use. Please review the following warnings before using an older version:

Adds the Pipeline step ‘input’ to wait for human input or approval.

A component of Pipeline Plugin.


2.11 (Aug 27, 2019)

  • JENKINS-47699: Allow user-scope credentials to be used as input step parameters.
  • Internal: Replace uses of deprecated APIs (PR 37)

2.10 (Mar 18, 2019)

  • Trim submitter names before making comparisons to avoid issues with whitespace (PR 30)
  • Add internationalization support (PR 23)
  • Internal: Update dependencies and fix resulting test failures so that the plugin's tests pass successfully when run using the PCT (PR 31)

2.9 (Dec 14, 2018)

  • JENKINS-55181 Compare the ID of the user attempting to submit an input step against the list of valid submitters using the IdStrategy and GroupIdStrategy configured by the current security realm. Previously, these comparisons were always case-sensitive.

2.8 (Aug 7, 2017)

2.7 (Apr 26, 2017)

  • JENKINS-43856 NoSuchMethodError from Blue Ocean code after the change in 2.6.

  • JENKINS-40594 The submitterParameter option added in 2.4 did not show the correct kind of hyperlink in the console unless parameters was also specified.

2.6 (Apr 24, 2017)

  • JENKINS-40926 API to retrieve parameters of a particular submission. No user-visible change.

2.5 (Nov 09, 2016)

  • 2.4 was corrupt.

2.4 (Nov 09, 2016)

  • JENKINS-31425 The submitter parameter now accepts a comma-separated list.
  • JENKINS-31396 submitterParameter parameter added.
  • JENKINS-38380 Interrupting an input step, for example with timeout, did not generally work in a secured system.

Use 2.5 instead.

2.3 (Oct 21, 2016)

  • JENKINS-39168 Exception thrown under some conditions from fix in 2.2.

2.2 (Oct 20, 2016)

2.1 (Aug 08, 2016)

  • JENKINS-37154 Deadlock under some conditions when aborting a build waiting in input.

2.0 (Apr 05, 2016)


  1. Unknown User (hujirong)

    We use https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin with AD groups to control the access to folders. When I use the following: 

    input message: 'Approve deploy to DEV?', submitter: 'WebDevelopers'

    "WebDevelopers" is our AD group name. I see this behaviour:

    1. A user belong to the group is allow to "Proceed" and "Abort". This is expected.
    2. A user NOT belong to the group receives no response when clicking "Proceed", but click "Abort" will fail the build as Finished: ABORTED. The later is not expected, and I want to see a message saying something like "NOT Allowed" for the former.

  2. Unknown User (zdtsw)

    I cannot see "Proceed" or "Abort" when hove over some stage from Pipeline view . And I think it only happens when  the previous stage uses parallel 

    But if I check console, it has "Proceed or Abort" waiting for me to pick.

    So the only way in my case is to go to console and do my choice there.

  3. Unknown User (tkleiber)

    Is there some way to release an input step remotely?

    We have the requirement to release normally in dependeny from another system an sometimes manually.