I have a submodule in a project in Jenkins. I've enabled the advanced setting to recursively update submodules.
When I run the build, I see that the workspace has the files from the submodule. The problem is, it seems to be the first revision of the submodule. When I push changes (repository hosted on GitHub) Jenkins doesn't seem to update the submodule to get the right changes. Has anyone ever seen this?
Note that the Jenkins Git plugin 2.0 will have "advance submodule behaviors", which should ensure proper updates of the submodules:
As commented by vikramvi
:
Advanced sub-modules behavior
> "Path of the reference repo to use during submodule update
" against this field , add submodule git url.
Owen B mentions in the comments:
For the authentication issue, there's now a "Use credentials from default remote of parent repository" option
Seen here in JENKINS-20941:
This is covered in the Git Plugin documentation on the Jenkins site under the section: Recursive submodules.
excerptThe GIT plugin supports repositories with submodules which in turn have submodules themselves. This must be turned on though: in Job Configuration -> Section Source Code Management, Git -> Advanced Button (under Branches to build) -> Recursively update submodules.
From the configuration screen of your job, in the Source Code Management section, pull the Add button down select "Advanced sub-modules behavior".
Then select "Recursively update submodules":
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With