Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
-
-
git plugin 4.7.0 released 17 Mar 2021
Description
This looks like the same type of code-path issue described in https://issues.jenkins-ci.org/browse/JENKINS-41996
@Library('someGitLibrary') node { final scmVars = checkout(scm) // scmVars may have Git data from either the someGitLibrary or the scmVars }
Looks like its caused by https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L1282-L1317
Attachments
Issue Links
- duplicates
-
JENKINS-53346 GitSCM checkout returns same values on second different call
-
- Closed
-
- is blocked by
-
JENKINS-52378 Revision state returned by Git SCM step is incorrect
-
- Closed
-
This is not limited to git.
We see the same or a very similar issue using an SVN repo (which includes svn:externals) and shared libraries stored in SVN.
The values returned by def checkoutResults = checkout(scm ...) contain SVN revision numbers that are not the SVN revision checked out.
Since we use this information in the generated Manifest files this is a major problem.