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

Parameterized Trigger still occupy node when using dynamic job name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Plugin 787.v665fcf2a_830b_, jenkins:2.451

      It still occupies the execution node after doing Trigger parameterized build on other projects ,when the secondary job is runing or waiting for it's nodes.

      After testing in a new jenkins machine ,it seems only happenning when one job trigger another job using dynamic variable job name.

            Unassigned Unassigned
            catkingfirst qingyi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: