Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32625

Option to run on the same node with naginator

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • naginator-plugin
    • 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

          ikedam added a comment -

          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?

          ikedam added a comment - 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?

            Unassigned Unassigned
            jeanfred Jean-Frédéric
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: