• 1.0-m10, 1.0-m11, 1.0-m12, 1.0-pre-beta-1, 1.0-beta-1

      https://projects.invisionapp.com/share/WA699WS3J#/screens

      In scope

      • Add the "Re-run" button to the top
      • Screen should transition to executing page state (UX-72)
      • Note that a "re-run" will create a new run result and the screen will have to update for that new run.
      • The re-run button should only appear for multi-branch pipelines (you can use the same logic for UX-208 to test for branch and PR support)
      • When you click the Rerun button the button label should transition to "Running..." and be disabled. When it starts being queued or running the button disappears.

      Out of scope:

      • Everything else.

          [JENKINS-35789] Developer can re-run a completed pipeline

          Cliff Meyers added a comment -

          Regarding the last requirement (transition to "Running..."), I omitted this in the first pass since the server queues the item more or less immediately and the page immediately refreshes with the new run.

          Cliff Meyers added a comment - Regarding the last requirement (transition to "Running..."), I omitted this in the first pass since the server queues the item more or less immediately and the page immediately refreshes with the new run.

          Cliff Meyers added a comment -

          Cliff Meyers added a comment - PR: https://github.com/jenkinsci/blueocean-plugin/pull/448

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

              Created:
              Updated:
              Resolved: