|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
For me, the solution was to update the sub-modules in a batch script prior to the build. I created a new SSH keypair and saved the public key to the bitbucket user (keypair saved to C:\users\USERNAME\.ssh) Then I ssh'd into [email protected] to generate a known_hosts file. Since Jenkins runs as a Windows service, I copied my SSH keys (id_rsa, id_rsa.pub, known_hosts) from C:\users\USERNAME\.ssh to C:\Windows\SysWOW64\config\systemprofile\.ssh.
After that was all sorted, I added a build step (needs to be the first build step). I created a Windows batch command that contained the following entries:
git config submodule.SUBMODULENAME.url [email protected]:SUBMODULE/DIRECTORY.git <-- ssh access url
git submodule update --init --recursive