[JIRA] (JENKINS-57472) Parameterized Trigger: incorrectly sets node label to master if node disconnects

2 views
Skip to first unread message

nelson.work@gmail.com (JIRA)

unread,
May 14, 2019, 5:03:02 PM5/14/19
to jenkinsc...@googlegroups.com
Elliot Nelson created an issue
 
Jenkins / Bug JENKINS-57472
Parameterized Trigger: incorrectly sets node label to master if node disconnects
Issue Type: Bug Bug
Assignee: Unassigned
Components: parameterized-trigger-plugin
Created: 2019-05-14 21:02
Environment: Jenkins 2.138.2, Plugin 2.35.2, Java 1.8.x, Linux
Labels: jenkins plugin slave
Priority: Minor Minor
Reporter: Elliot Nelson

If Project A triggers Project B on same node, but while Project A is running the build agent it is running on disconnects abnormally (machine disconnect, network issue, etc.), what happens is that Project B is triggered on master instead of the target node.

 

The expected behavior is that Project B is triggered with the original node label, and ends up in the queue waiting for the target machine to reconnect, since it is no longer connected.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

o.v.nenashev@gmail.com (JIRA)

unread,
Dec 10, 2019, 6:23:03 PM12/10/19
to jenkinsc...@googlegroups.com
Oleg Nenashev resolved as Fixed
Change By: Oleg Nenashev
Status: Open Resolved
Resolution: Fixed
Released As: Parameterized Trigger 2.36
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages