-
New Feature
-
Resolution: Unresolved
-
Major
In multibranch jobs, if you 'replay' a build it will reuse the git commit (and assume svn revision etc) of the build in the replay.
But with non-multibranch pipeline jobs, the latest commit is always used no matter what build is replayed.
It may have something to do with 'checkout scm' vs 'git url:' being used, but either way I think it should work in the same.
- is duplicated by
-
JENKINS-45808 "checkout scm" should give the same guarantees on standalone pipeline jobs as on multibranch jobs
-
- Resolved
-
[JENKINS-36453] Replay does not reuse commit on non-multibranch pipeline jobs
Labels | New: blueocean |
Description |
Original:
In multibranch jobs, if you 'replay' a build it will reuse the git commit (and assume svn revision etc) of the build in the replay. But with non-multibranch pipeline jobs, the latest commit is always used no matter what build is replayed. It may have something to do with 'checkout scm' vs 'git url:' being used, but either way I think it should work ine same. |
New:
In multibranch jobs, if you 'replay' a build it will reuse the git commit (and assume svn revision etc) of the build in the replay. But with non-multibranch pipeline jobs, the latest commit is always used no matter what build is replayed. It may have something to do with 'checkout scm' vs 'git url:' being used, but either way I think it should work in the same. |
Workflow | Original: JNJira [ 173161 ] | New: JNJira + In-Review [ 184975 ] |
Component/s | New: pipeline-general [ 21692 ] |
Component/s | Original: workflow-plugin [ 18820 ] |
Component/s | New: workflow-cps-plugin [ 21713 ] | |
Component/s | Original: pipeline [ 21692 ] | |
Assignee | Original: Jesse Glick [ jglick ] | |
Issue Type | Original: Improvement [ 4 ] | New: New Feature [ 2 ] |
Link |
New:
This issue is duplicated by |
Replay is actually not the central issue. scm for a CpsScmFlowDefinition is not guaranteed to match the commit of Jenkinsfile. This is because it is using hudson.model.SCM, i.e., the old core APIs, which do not support checking out a specific version. In order to fix this we would have to actually deprecate CpsScmFlowDefinition and provide a replacement using scm-api so it would behave more like multibranch, except of course for a predefined branch.