Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63820

No flow execution for input in lock block after restart


      After restart, having input step inside lock and several jobs waiting to acquire the lock, not able to Proceed or Abort anymore.

      Steps to reproduce:
      1) Have "input" inside a lock block
      2) Start several build of the same job (the earliest will block on "input" and others block on "lock")
      3) Restart Jenkins

      Observed behaviour:
      Can not Proceed or Abort the build with buttons anymore. Even generic abort button does not work for the build, have to "kill" it.

      Expected behaviour:
      One can Proceed or Abort the build.

      Minimal pipeline to reproduce:

      pipeline {
          agent none
          stages {
              stage('a') {
                  steps {
                      lock('lock-me-in') {
                          script {
                              input 'Are you okay?'

      Output in the jenkins log:

      WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction:  no flow execution found for input-simple #8

            Unassigned Unassigned
            ysoldak Yurii Soldak
            3 Vote for this issue
            6 Start watching this issue