|
||||||||
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 |
- [JIRA] (JENKINS-14201) Git submodules che... m...@monki.org.uk (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... a...@birkett.co.uk (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... a...@birkett.co.uk (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... skomatsu.com...@gmail.com (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... skomatsu.com...@gmail.com (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... skomatsu.com...@gmail.com (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... skomatsu.com...@gmail.com (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... skomatsu.com...@gmail.com (JIRA)
- [JIRA] (JENKINS-14201) Git submodule... skomatsu.com...@gmail.com (JIRA)
I'm seeing the same issue, compounded by the fact that even clearing down the workspace doesn't resolve the problem. In the output below (censored for security/privacy reasons, intent is the same). origin/requirejs-2.0-upgrade is not part of REMOVEDPROJECT-pkg, but a branch in the submodule contained with in.
This did work, but after changing the submodule locations and updating via git submodule sync each build gets the following error.
Work around will be to add a git checkout as a manual step, so not entirely a blocker but a significant problem none the less.