-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins 2.17, Git Plugin 3.0.0, Git Client Plugin 2.0.0
I tried to use somehow simplified names for some submodules having more complex path in worktree, ending up in a broken build, as git plugin tries to update-init them using their name instead of their path. leading to a unknown submodule error.
- is related to
-
JENKINS-37419 Git plugin checking out non-existent submodule from different branch
-
- Closed
-
[JENKINS-37495] [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout
Assignee | Original: Mark Waite [ markewaite ] |
Labels | Original: git workflow | New: git pipeline workflow |
Labels | Original: git pipeline workflow | New: git pipeline |
Comment | [ Thanks. Since a work around is available, I'll leave the detailed investigation of this for another time. ] |
Assignee | New: Mark Waite [ markewaite ] |
Link |
New:
This issue is related to |
Environment | Original: Jenkins 2.17, Git Plugin 3.0.0-beta2 | New: Jenkins 2.17, Git Plugin 3.0.0, Git Client Plugin 2.0.0 |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Summary | Original: Git Submodules having a name different to their path in working tree, failing to checkout | New: [REGRESSION] Git Submodules having a name different to their path in working tree, failing to checkout |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |