-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
I am using the `same-node` parameter of the “Trigger parameterized builds” so that with jobA→jobB, jobB runs on the same node as jobA. However, if jobB fails and I use Naginator to retry it, it sometimes builds on another node, failing the job.
[JENKINS-32625] Option to run on the same node with naginator
Assignee | Original: Nicolas De Loof [ ndeloof ] | New: ikedam [ ikedam ] |
Assignee | Original: ikedam [ ikedam ] | |
Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
Summary | Original: Naginator plugin does not keep node information | New: Option to run on the same node with naginator |
Workflow | Original: JNJira [ 168282 ] | New: JNJira + In-Review [ 183050 ] |
It's caused for naginator-plugin replays only build parameters,
and it doesn't replay the node-specifying feature provided by parameterized-trigger-plugin.
(It is called a "parameter" in UI, but actually is not a build parameter.)
Node Label Parameter plugin may help you, as it implements the node-specifying feature as a build parameter, and can be replayed with naginator-plugin.
Would you see whether it helps you?