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

API allows re-running of a completed run with the same commits

    Details

    • Similar Issues:
    • Epic Link:
    • Sprint:
      1.0-m10, 1.0-m11

      Description

      In Scope

      • New rerun action in the rest API that can take the commits of a completed run and execute a new run with those exact commits.
      • This should work for multi-branch pipeline jobs
      • Ideally I'd like to see this work for other jobs too (such as Freestyle) if it isn't too much work
      • If this does not work for all job types, the UI will need some way of testing if re-runs are supported (so we can show the button or not) – We should consider UX-350

        Attachments

          Issue Links

            Activity

            Hide
            jamesdumay James Dumay added a comment -

            Ivan Meredith is it still true that UX-158 blocks this work?

            Show
            jamesdumay James Dumay added a comment - Ivan Meredith is it still true that UX-158 blocks this work?
            Hide
            michaelneale Michael Neale added a comment -

            NOTE: Ivan Meredith James Dumay if you use "Replay" feature as it is today, it will actaully run it with the same commit, so this is essentially the same as https://cloudbees.atlassian.net/browse/UX-416 - only in one case you provide an alternative Jenkinsfile content, in another case you don't change it - but same result.

            Perhaps we should close this as a duplicate of https://cloudbees.atlassian.net/browse/UX-416 - and track it there?
            I don't think replay works with freestyle, or plain pipeline jobs, so that may be a limitation (in which case, all the api could do is re-run the job, not with a specific commit, and I would be ok with that limitation).

            Show
            michaelneale Michael Neale added a comment - NOTE: Ivan Meredith James Dumay if you use "Replay" feature as it is today, it will actaully run it with the same commit, so this is essentially the same as https://cloudbees.atlassian.net/browse/UX-416 - only in one case you provide an alternative Jenkinsfile content, in another case you don't change it - but same result. Perhaps we should close this as a duplicate of https://cloudbees.atlassian.net/browse/UX-416 - and track it there? I don't think replay works with freestyle, or plain pipeline jobs, so that may be a limitation (in which case, all the api could do is re-run the job, not with a specific commit, and I would be ok with that limitation).
            Hide
            jamesdumay James Dumay added a comment - - edited

            Nah keep UX-416 open - its a different use case entirely. I've gone ahead and linked the two.

            Show
            jamesdumay James Dumay added a comment - - edited Nah keep UX-416 open - its a different use case entirely. I've gone ahead and linked the two.
            Hide
            michaelneale Michael Neale added a comment -

            James Dumay they are different, but could be quite close both in experience and implementation, but one could argue that when you go to replay+edit, you are in "fix up build config" mode, vs "re-run against this commit to see if it is environmental failure" - different frames of mind when you do it, agree.

            Show
            michaelneale Michael Neale added a comment - James Dumay they are different, but could be quite close both in experience and implementation, but one could argue that when you go to replay+edit, you are in "fix up build config" mode, vs "re-run against this commit to see if it is environmental failure" - different frames of mind when you do it, agree.
            Hide
            jamesdumay James Dumay added a comment - - edited

            [~mneale] I still think the modify+rerun is very important. For the sake of brevity I just want to split these problems out for the moment.

            Show
            jamesdumay James Dumay added a comment - - edited [~mneale] I still think the modify+rerun is very important. For the sake of brevity I just want to split these problems out for the moment.
            Hide
            imeredith Ivan Meredith added a comment -

            Blocked by an issue in workflow plugin. PR submitted

            Show
            imeredith Ivan Meredith added a comment - Blocked by an issue in workflow plugin. PR submitted
            Show
            michaelneale Michael Neale added a comment - Associated PR: https://github.com/jenkinsci/workflow-cps-plugin/pull/27
            Hide
            jamesdumay James Dumay added a comment -

            Ivan Meredith workflow-cps 2.8 has been released with your changes.

            Show
            jamesdumay James Dumay added a comment - Ivan Meredith workflow-cps 2.8 has been released with your changes.

              People

              • Assignee:
                imeredith Ivan Meredith
                Reporter:
                jamesdumay James Dumay
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: