- 
    Bug 
- 
    Resolution: Not A Defect
- 
    Minor 
- 
    None
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