Parameterized Trigger still occupy node when using dynamic job name

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Unassigned
            Reporter:
            qingyi
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: