One critical feature is the ability to take a run, say a failed run, and tweak the Jenkinsfile, and run it again, without having to change the Jenkinsfile and push and trigger a build.

      this is CRITICAL for making Jenkinsfile practical, a feature which is heavily used by those that know about it.

      This can work by having an option that pops over "Replay and alter pipeline" (it could be grouped with "replay", just an option to tweak the Jenkinsfile).

      An ACE based editor could then popup allowing small changes, and then run it (in which case it goes immediately to the results/running screen for that new run).

      Once a user is happy with the result, it is up to them to grab the changes and paste them into their Jenkinsfile, so making it clear that they can click and view the Jenkinsfile once their replay has finished is also important.

          [JENKINS-35801] Replay of a run with modified Jenkinsfile

          Michael Neale added a comment -

          jdumay dogfood has taught me this is absolutely must have for a 1.0.

          Michael Neale added a comment - jdumay dogfood has taught me this is absolutely must have for a 1.0.

          James Dumay added a comment -

          mneale let's do an exploration of that IDE style thing

          James Dumay added a comment - mneale let's do an exploration of that IDE style thing

          Michael Neale added a comment -

          jdumay sure - but don't want this to be a big thing. It has to be simple, the basics.

          Michael Neale added a comment - jdumay sure - but don't want this to be a big thing. It has to be simple, the basics.

          James Dumay added a comment -

          hrmpw and I would like this replay-modified-jenkinsfile functionality to work within the editor.

          James Dumay added a comment - hrmpw and I would like this replay-modified-jenkinsfile functionality to work within the editor.

          Isn't this done as the "replay" link on a given build?  Or did I misunderstand something?

          Christian Höltje added a comment - Isn't this done as the "replay" link on a given build?  Or did I misunderstand something?

          Reinhold Füreder added a comment - - edited

          docwhat yes, I guess it is the "replay" in classic UI; and this issue is about adding this to new/modern Blue Ocean UI.

          Hm, but what is the "rerun" (on a given pipeline) in Blue Ocean UI then? Is it the "replay" without possibility to adapt the "Jenkinsfile"?

          Reinhold Füreder added a comment - - edited docwhat yes, I guess it is the "replay" in classic UI; and this issue is about adding this to new/modern Blue Ocean UI. Hm, but what is the "rerun" (on a given pipeline) in Blue Ocean UI then? Is it the "replay" without possibility to adapt the "Jenkinsfile"?

          Michael Neale added a comment -

          reinholdfuereder exactly - it replays the exact commit but without the ability (yet) to tweak the Jenkinsfile. To me this seems wrong. most of the time it is fine to just run it from the head of the branch again. When there is support to replay and edit, sure, maybe that makes sense (if debugging a flaky build)

          Michael Neale added a comment - reinholdfuereder exactly - it replays the exact commit but without the ability (yet) to tweak the Jenkinsfile. To me this seems wrong. most of the time it is fine to just run it from the head of the branch again. When there is support to replay and edit, sure, maybe that makes sense (if debugging a flaky build)

            Unassigned Unassigned
            jamesdumay James Dumay
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: