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

Re-triggering a failed build copies the Actions from previous builds

XMLWordPrintable

      Steps to reproduce:

      1. Create a build pipeline with at least two stages, the second of which adds Actions to a build. For example, the git-plugin will attach a hudson.plugins.git.GitTagAction to the build to say what revision was built.
      2. Run the pipeline
      3. Re-run the second stage of the pipeline

      Expect:

      1. One actions in the summary page of the build from the git plugin

      Observe:

      1. Two actions! The previous builds action and the current builds (see attached screenshot)

      Marking as major because this results in breaking the TestNG publisher plugin - it relies on actions being persisted in builds to show reports and trend data. When actions are copied, the data is corrupted, and trends are overridden. This could potentially break other plugins in the pipeline as well.

        1. JENKINS-30801.png
          JENKINS-30801.png
          169 kB

          [JENKINS-30801] Re-triggering a failed build copies the Actions from previous builds

          Dan Alvizu created issue -
          Dan Alvizu made changes -
          Attachment New: JENKINS-30801.png [ 30791 ]

          Dan Alvizu added a comment -

          Some search terms to help other folks:

          • duplicate git build data / multiple git build data
          • duplicate git revision / multiple git revision
          • duplicate testng results
          • testng results overridden in build pipeline

          Dan Alvizu added a comment - Some search terms to help other folks: duplicate git build data / multiple git build data duplicate git revision / multiple git revision duplicate testng results testng results overridden in build pipeline
          Dan Alvizu made changes -
          Summary Original: Re-triggering a failed build results in Actions duplicated from previous build New: Re-triggering a failed build copies the Actions from previous builds

          Dan Alvizu added a comment -

          PR: https://github.com/jenkinsci/build-pipeline-plugin/pull/89

          Dan Alvizu added a comment - PR: https://github.com/jenkinsci/build-pipeline-plugin/pull/89
          Dan Alvizu made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Dan Alvizu made changes -
          Assignee New: Dan Alvizu [ dalvizu ]
          Dan Alvizu made changes -
          Description Original: Steps to reproduce:
          # Create a build pipeline with at least two stages, the second of which adds Actions to a build. For example, the git-plugin will attach a {{hudson.plugins.git.GitTagAction}} to the build to say what revision was built.
          # Run the pipeline
          # Re-run the second stage of the pipeline

          Expect:
          # One actions in the summary page of the build from the git plugin
          # Two actions! The previous builds action and the current builds (see attached screenshot)

          Marking as major because this results in breaking the TestNG publisher plugin - it relies on actions being persisted in builds to show reports and trend data. When actions are copied, the data is corrupted, and trends are overridden. This could potentially break other plugins in the pipeline as well.
          		 New: Steps to reproduce:
          # Create a build pipeline with at least two stages, the second of which adds Actions to a build. For example, the git-plugin will attach a {{hudson.plugins.git.GitTagAction}} to the build to say what revision was built.
          # Run the pipeline
          # Re-run the second stage of the pipeline

          Expect:
          # One actions in the summary page of the build from the git plugin

          Observe:
          # Two actions! The previous builds action and the current builds (see attached screenshot)

          Marking as major because this results in breaking the TestNG publisher plugin - it relies on actions being persisted in builds to show reports and trend data. When actions are copied, the data is corrupted, and trends are overridden. This could potentially break other plugins in the pipeline as well.
          Dan Alvizu made changes -
          Link New: This issue is related to JENKINS-22210 [ JENKINS-22210 ]
          Dan Alvizu made changes -
          Link New: This issue is related to JENKINS-24883 [ JENKINS-24883 ]

            dalvizu Dan Alvizu
            dalvizu Dan Alvizu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: