[JIRA] (JENKINS-60591) checkout scm doesn't take revision that started the pipeline

[mushko1...@gmail.com (JIRA)]

Title: Message Title

Mykhailo Zolotarenko created an issue   Jenkins / JENKINS-60591 checkout scm doesn't take revision that started the pipeline Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-12-26 17:49 Priority: Minor Reporter: Mykhailo Zolotarenko checkout scm doesn't take revision that started the pipeline instead takes last (fresh) commit from branch Related to doc: https://jenkins.io/doc/book/pipeline/jenkinsfile/ The checkout step will checkout code from source control; scm is a special variable which instructs the checkout step to clone the specific revision which triggered this Pipeline run.   To reproduce: Merge to branch (abc) start pipeline pipeline waits for continue (input message) push new change to branch (xyz) resume pipeline Expect: pipeline resume abc Observe: pipeline resume xyz   Workaround for as - use explicit checkout git commit variable GIT_COMMIT we defined at the beginning of Pipeline:  def scmVars = checkout scm env.GIT_COMMIT = scmVars.GIT_COMMIT   And we see that checkout show different results:   checkout scm: [$class: 'GitSCM', branches: [[name: "${GIT_COMMIT}"]]] sh 'cat new_files' // abc   checkout scm sh 'cat new_files' // xyz   It's a bug or feature? according to the doc - bug... (git plugin?)   Can be related with JENKINS-59071 or JENKINS-43761   Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203813.1577382573000.298.1577382600340%40Atlassian.JIRA.