• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: parameterized-trigger-plugin
• Labels:

  None
• Environment:

  Plugin 787.v665fcf2a_830b_, jenkins:2.451

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

qingyi created issue - 2024-04-02 07:13

qingyi made changes - 2024-04-02 07:17

Summary

Original: Parameterized Trigger

New: Parameterized Trigger still occpuy node

qingyi made changes - 2024-04-02 07:17

Summary

Original: Parameterized Trigger still occpuy node

New: Parameterized Trigger still occupy node

qingyi made changes - 2024-04-02 11:46

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 - 2024-04-02 11:51

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