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

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

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • None

      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.

          [JENKINS-29765] Build Retry (both Naginator and Rebuild) pick the latest commit, not retrying one

          Eric Griswold created issue -
          Eric Griswold made changes -
          Description Original: 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
          * Commit and run a build. It should fail. Note Git SHA (This is build #1)
          * Make a second build and run it. It should also fail. Note the Git SHA (This is build #2)
          * Now go back to build #1 and retrigger it.

          My expectation is that the retriggered build should have the same Git SHA as build #1. When I try it, the Git SHA is the HEAD of the branch at the time of the retrigger.
          New: 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
          * Commit and run a build. It should fail. Note Git SHA (This is build #1)
          * Make a second build and run 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 have the same Git SHA as build #1.

          Observed problem:

          The Git SHA is the HEAD of the branch at the time of the retrigger.
          Eric Griswold made changes -
          Description Original: 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
          * Commit and run a build. It should fail. Note Git SHA (This is build #1)
          * Make a second build and run 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 have the same Git SHA as build #1.

          Observed problem:

          The Git SHA is the HEAD of the branch at the time of the retrigger.
          New: 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 have the same Git SHA as build #1.

          Observed problem:

          The Git SHA is the HEAD of the branch at the time of the retrigger.
          Eric Griswold made changes -
          Description Original: 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 have the same Git SHA as build #1.

          Observed problem:

          The Git SHA is the HEAD of the branch at the time of the retrigger.
          New: 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.
          Mattias Vannergård made changes -
          Component/s New: git-plugin [ 15543 ]
          Mattias Vannergård made changes -
          Environment Original: Standalone CentOS 7 machine. Jenkins 1.622; Git plugin 2.4.0; Naginator 1.15; rebuilder 1.25

          Replicated on a CentOS 6 machine. Jenkins 1.580.3; Git plugin 2.3.5; Naginator 1.14; Rebuilder 1.22
          New: Standalone CentOS 7 machine. Jenkins 1.622; Git plugin 2.4.0; Naginator 1.15; rebuilder 1.25

          Replicated on a CentOS 6 machine. Jenkins 1.580.3; Git plugin 2.3.5; Naginator 1.14; Rebuilder 1.22

          Replicated on a Win 7 machine. Jenkins 1.596.2; Git plugin 2.4.0; Gerrit plugin 2.16.0; Rebuilder 1.25 (I do have Naginator 1.15 installed, but it is not involved in this job)
          Mark Waite made changes -
          Component/s Original: git-plugin [ 15543 ]
          Component/s Original: core [ 15593 ]
          Mattias Vannergård made changes -
          Component/s New: gerrit-trigger-plugin [ 15731 ]
          Component/s New: git-plugin [ 15543 ]
          Mark Waite made changes -
          Component/s Original: git-plugin [ 15543 ]
          Mark Waite made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]
          Mattias Vannergård made changes -
          Component/s Original: gerrit-trigger-plugin [ 15731 ]

            Unassigned Unassigned
            eegah Eric Griswold
            Votes:
            14 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: