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

Developer can run a new build and rerun from a card

    XMLWordPrintable

Details

    • 1.0-pre-beta-1, 1.0-beta-1

    Description

      In Scope

      • Developer can click the rerun icon on a favourite card and re-queue the same commit
      • Developer can click the "play" icon on a favourite card and queue a new run
      • Run icon should appear next to the left of the favourite action and to the right of the re-run action
      • Play icon appears on all cards
      • Behaviour must be as defined in JENKINS-36424

      Attachments

        Issue Links

          Activity

            cliffmeyers Cliff Meyers added a comment -

            jamesdumay Does it make sense to display the "Run" icon and "Re-run" icon at the same time? If so, what would the difference in behavior be? Since we are always showing the latest build in the card, I assume that clicking either of these buttons will just re-run the proper pipeline (or branch, if multi-branch)? If that's the case, it probably makes sense to show "Re-run" for anything that is "failed" and "Run" for anything that was successful?

            cliffmeyers Cliff Meyers added a comment - jamesdumay Does it make sense to display the "Run" icon and "Re-run" icon at the same time? If so, what would the difference in behavior be? Since we are always showing the latest build in the card, I assume that clicking either of these buttons will just re-run the proper pipeline (or branch, if multi-branch)? If that's the case, it probably makes sense to show "Re-run" for anything that is "failed" and "Run" for anything that was successful?
            jamesdumay James Dumay added a comment -

            cliffmeyers rerunning will re-run the pipeline using the same commit. Running will make it run with the latest commit.

            Re-run is only supported in the multbranch pipeline case - imeredith can probably help answer any questions there.

            jamesdumay James Dumay added a comment - cliffmeyers rerunning will re-run the pipeline using the same commit. Running will make it run with the latest commit. Re-run is only supported in the multbranch pipeline case - imeredith can probably help answer any questions there.
            cliffmeyers Cliff Meyers added a comment -

            jamesdumay it looks like "rerun" (aka the /replay API) works for pipelines and multi-branch pipelines. If so, should we enable it for both, or stick with MBP only? Thanks.

            cliffmeyers Cliff Meyers added a comment - jamesdumay it looks like "rerun" (aka the /replay API) works for pipelines and multi-branch pipelines. If so, should we enable it for both, or stick with MBP only? Thanks.
            cliffmeyers Cliff Meyers added a comment -

            Marked as blocked by JENKINS-36376 since we want to use the capabilities API to drive this and right now we'd need to key off the _class value, which we are trying to avoid.

            cliffmeyers Cliff Meyers added a comment - Marked as blocked by JENKINS-36376 since we want to use the capabilities API to drive this and right now we'd need to key off the _class value, which we are trying to avoid.
            jamesdumay James Dumay added a comment -

            cliffmeyers if it works for both then you can show it for both

            jamesdumay James Dumay added a comment - cliffmeyers if it works for both then you can show it for both
            cliffmeyers Cliff Meyers added a comment - PR: https://github.com/jenkinsci/blueocean-plugin/pull/417

            People

              cliffmeyers Cliff Meyers
              jamesdumay James Dumay
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: