Status: Open (View Workflow)
If you create a project that has a relative submodule path. Say this is hosted in your personal github space:
The subproject it part of the mainproject with an entry link this in the .gitmodules:
path = subproject
url = ../subproject.git
Using relative URLs has many benefits, a primary one being the checkout works over any protocol.
If you setup a jenkins job to build mainproject everything works fine, if the project is then move to a different github account (say to your employers organisation):
Changing the URL the jenkins jobs works for pulling in changes from mainproject, but when submodule updates are attempted the old url still gets used. This seems to be because the origin remote in the mainproject repository doesn't get updated with the new URL and so all the relative URLs remain relative to that project.
- is related to
JENKINS-8503 Git submodules are cloned too early and not removed once the revToBuild has been checked out
JENKINS-63049 Git fetch fails if submodule URL changed
|Field||Original Value||New Value|
|Link||This issue is related to JENKINS-8503 [ JENKINS-8503 ]|
|Workflow||JNJira [ 146133 ]||JNJira + In-Review [ 176540 ]|
|Assignee||Nicolas De Loof [ ndeloof ]|
This issue is related to