[JIRA] (JENKINS-61317) env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT

[foreverbonfy@gmail.com (JIRA)]

bon ch created an issue

Jenkins / JENKINS-61317 env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2020-03-04 04:37 Priority: Major Reporter: bon ch env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）   SharedLibrary put in the same code repo, different branch named xxx_lib, and after Declarative: Checkout SCM, can not get the right GIT_COMMIT, always be the xxx_lib's last commit, not the code's commit Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-61317 env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-61317

Re: env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT Please provide an example pipeline which shows the issue using a publicly accessible git repository.

Add Comment

[foreverbonfy@gmail.com (JIRA)]

bon ch commented on JENKINS-61317

Re: env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT

Mark Waite I create example repo to this issue: https://github.com/bonfy/JENKINS-61317 Jenkinsfile in master branch Last commit : 64dd9920 library in jenkins-lib branch Last commit: a8c235b1 and when echo GIT_COMMIT, it is overwitten by lib's commit [Pipeline] echo 13:22:18 stage 1 [Pipeline] echo 13:22:18 GIT COMMIT : a8c235b10c55e2f065293b1c1ad9b3bffd45d9d9 [Pipeline] echo 13:22:18 Hello world [Pipeline] }

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-61317

Re: env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT

Thank you.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite edited a comment on JENKINS-61317

Re: env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT

Thank you.   Until a fix is available for the issue, you can use the {{returnStdout}} capability of the {{sh}} and {{bat}} and {{powershell}} commands to call {{git rev-parse HEAD}}

Add Comment

[foreverbonfy@gmail.com (JIRA)]

bon ch commented on JENKINS-61317

Re: env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT

ok, thx

Add Comment

[foreverbonfy@gmail.com (JIRA)]

bon ch commented on JENKINS-61317

Re: env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT

Mark Waite   I update the repo https://github.com/bonfy/JENKINS-61317 Add echo env.GIT_BRANCH, and find that the GIT_BRANCH is also overwritten, maybe other git related env valuables as well.  So maybe you can check and fix them together.   the Jenkins console output now looks like:    16:55:47 stage 1 [Pipeline] echo 16:55:47 GIT COMMIT : a8c235b10c55e2f065293b1c1ad9b3bffd45d9d9 [Pipeline] echo 16:55:47 GIT BRANCH : jenkins-lib [Pipeline] echo 16:55:48 Hello world   Thanks

Add Comment

[foreverbonfy@gmail.com (JIRA)]

bon ch updated an issue

Jenkins / JENKINS-61317

env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT

Change By: bon ch

env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）

SharedLibrary put in the same code repo, different branch named xxx_lib, and after Declarative: Checkout SCM, can not get the right GIT_COMMIT, always be the xxx_lib's last commit, not the code's commit

I create example repo to this issue: [https://github.com/bonfy/JENKINS-61317]

Jenkinsfile in master branch Last commit: 39f25e1a

library in jenkins-lib branch Last commit: a8c235b1 and when echo GIT_COMMIT, it is overwitten by lib's commit [Pipeline] echo 13:22:18 stage 1 [Pipeline] echo

13:22:18 GIT COMMIT : a8c235b10c55e2f065293b1c1ad9b3bffd45d9d9 [Pipeline] echo

13:22:18 Hello world [Pipeline] }

Add Comment

[foreverbonfy@gmail.com (JIRA)]

bon ch updated an issue

Jenkins / JENKINS-61317 env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）, can not get the right GIT_COMMIT Change By: bon ch

env.GIT_COMMIT is overwritten when pull lib （lib and code in the same repo）   SharedLibrary put in the same code repo, different branch named xxx_lib, and after Declarative: Checkout SCM, can not get the right GIT_COMMIT, always be the xxx_lib's last commit, not the code's commit     I create example repo to this issue: [https://github.com/bonfy/JENKINS-61317] Jenkinsfile in master branch Last commit: 39f25e1a library in jenkins-lib branch Last commit: a8c235b1 and when echo GIT_COMMIT, it is overwitten by lib's commit

[Pipeline] echo 13 16 : 22 55 : 18 47 stage 1 [Pipeline] echo 13 16 : 22 55 : 18 47 GIT COMMIT : a8c235b10c55e2f065293b1c1ad9b3bffd45d9d9 [Pipeline] echo 13 16 : 22 55 : 18 Hello world 47 GIT BRANCH : jenkins-lib [Pipeline]  } echo

16:55:48 Hello world

Add Comment