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

Pipeline input step should never use an executor

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • pipeline
    • None

      If a pipeline declares an agent/node for the whole pipeline or for a stage, an input step will automatically hold on to an executor. As a workaround you will have to define your agent/node declaration in a way that do not wrap the input step.

      I cannot think of a use case where you will ever want to hold on to an executor when waiting for a manual input. The approval process can take anywhere from minutes, days or even weeks. I think it's reasonable to say that the input step should handle the behavior internally by never run on an agent/node independent of the agent/node declaration.

      Please provide use cases where holding on to an executor makes sense for better understanding in case I am missing something.

            Unassigned Unassigned
            bmuchko Benjamin Muschko
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: