Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
Description
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.
Attachments
Issue Links
- is duplicated by
-
JENKINS-45808 "checkout scm" should give the same guarantees on standalone pipeline jobs as on multibranch jobs
-
- Resolved
-
Activity
Ivan Meredith
created issue -
| Field | Original Value | New Value |
|---|---|---|
| Labels | blueocean |
Ivan Meredith
made changes -
| Description |
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. |
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 | JNJira [ 173161 ] | JNJira + In-Review [ 184975 ] |
| Component/s | pipeline-general [ 21692 ] |
| Component/s | workflow-plugin [ 18820 ] |
| Component/s | workflow-cps-plugin [ 21713 ] | |
| Component/s | pipeline [ 21692 ] | |
| Assignee | Jesse Glick [ jglick ] | |
| Issue Type | Improvement [ 4 ] | New Feature [ 2 ] |
| Link |
This issue is duplicated by |
Nicos Maris
made changes -
| Priority | Minor [ 4 ] | Major [ 3 ] |