Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Not A Defect
-
None
Description
If new commits go into a repo after a build has started we find later stages running against a different commit to the earlier stages.
We've been using checkout scm + stash/unstash to work around this
I've made a test repo to demonstrate the issue: https://github.com/leth/jenkins-pipeline-scm-test
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Attachment | config.xml [ 34766 ] |
Attachment | consoleText.txt [ 34767 ] |
Resolution | Not A Defect [ 7 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |