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
    • parameterized-trigger-plugin
    • 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.

          [JENKINS-72950] Parameterized Trigger still occupy node when using dynamic job name

          qingyi created issue -
          qingyi made changes -
          Summary Original: Parameterized Trigger New: Parameterized Trigger still occpuy node
          qingyi made changes -
          Summary Original: Parameterized Trigger still occpuy node New: Parameterized Trigger still occupy node

          qingyi added a comment -

          The latest observation is that he'll wait until the follow-up task is complete and then print a message in the log.

          qingyi added a comment - The latest observation is that he'll wait until the follow-up task is complete and then print a message in the log.
          qingyi made changes -
          Description Original: It still occupies the execution node after doing Trigger parameterized build on other projects ,when the secondary job is waiting for it's nodes. New: It still occupies the execution node after doing Trigger parameterized build on other projects ,when the secondary job is waiting for it's nodes.

          After testing in a new jenkins machine ,it only happens when my job trigger a job using dynamic variable job name.
          qingyi made changes -
          Description Original: It still occupies the execution node after doing Trigger parameterized build on other projects ,when the secondary job is waiting for it's nodes.

          After testing in a new jenkins machine ,it only happens when my job trigger a job using dynamic variable job name.           		New: 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.
          Summary Original: Parameterized Trigger still occupy node New: Parameterized Trigger still occupy node when using dynamic job name

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

              Created:
              Updated: