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

Build Retry (both Naginator and Rebuild) pick the latest commit, not retrying one

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      This is easily reproduced on a standalone Cent 6 or Cent 7 machine.

      Create a job:

      • Uses Git
      • A trivial build step that fails, "false" or "exit 1" in the shell build-step for example
      • Uses one of the above retry mechanisms (Naginator or Rebuilder)
      • In the case of Naginator, stub it with a regex to keep it from automatically retrying
      • In the case of Rebuilder, enable the rebuild without parameters
      • Make a commit and run a build. It should fail. Note Git SHA (This is build #1)
      • Make a second commit, then build it. It should also fail. Note the Git SHA (This is build #2)
      • Now go back to build #1 and retrigger it. (build #3)

      Expectation:

      The retriggered build (build #3) should use the same Git SHA as build #1.

      Observed problem:

      The Git SHA is the HEAD of the branch at the time of the retrigger.

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          The Jenkins pipeline includes a capability called "Replay" which will run the same build again. I believe it uses the same SHA1 (or subversion commit) on a replay build as it did on the original build.

          Show
          markewaite Mark Waite added a comment - The Jenkins pipeline includes a capability called "Replay" which will run the same build again. I believe it uses the same SHA1 (or subversion commit) on a replay build as it did on the original build.
          Hide
          gst Grégory Starck added a comment -

          Hi,

          I'm facing the same problem in a jenkins project building lots of git branches where we have quite often activity (pushes).. really often there are failed jobs that I want to retry but effectively it's always the last build that was run which is retried, and not the one on which I actually retry ..

          any high level idea when this feature/bugfix could be foreseen/released :-?

          Many thx.

          Show
          gst Grégory Starck added a comment - Hi, I'm facing the same problem in a jenkins project building lots of git branches where we have quite often activity (pushes).. really often there are failed jobs that I want to retry but effectively it's always the last build that was run which is retried, and not the one on which I actually retry .. any high level idea when this feature/bugfix could be foreseen/released :-? Many thx.
          Hide
          markewaite Mark Waite added a comment -

          I have no plans to implement any changes to support this in the git plugin or the git client plugin. I believe the necessary API calls are already available, as evidenced by the pipeline "Replay" function. The pipeline "Replay" uses the same commit in the new build as was used in the original build.

          Show
          markewaite Mark Waite added a comment - I have no plans to implement any changes to support this in the git plugin or the git client plugin. I believe the necessary API calls are already available, as evidenced by the pipeline "Replay" function. The pipeline "Replay" uses the same commit in the new build as was used in the original build.
          Hide
          danielbeck Daniel Beck added a comment -

          as evidenced by the pipeline "Replay" function

          It stores the revision in the job config, which results in side effects such as polling being stupidly broken: JENKINS-40722

          Show
          danielbeck Daniel Beck added a comment - as evidenced by the pipeline "Replay" function It stores the revision in the job config, which results in side effects such as polling being stupidly broken: JENKINS-40722
          Hide
          mingfan ming fan added a comment -

          Have the same issue withJenkins ver. 2.77

          Show
          mingfan ming fan added a comment - Have the same issue withJenkins ver. 2.77

            People

            • Assignee:
              Unassigned
              Reporter:
              eegah Eric Griswold
            • Votes:
              13 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

              • Created:
                Updated: