Last modified: 2014-04-18 10:39:57 UTC
The scm > git > disable_submodule flag we are given by jenkins-job-builder results in the command "git submodule update". This means that when the workspace is created, no submodules are fetched because "update" only updates, it doesn't initialise. So when adding a new project with submodules, or adding (new) submodules to an existing project, they don't appear in the workspace on Jenkins. It could be that this is a bug in Jenkins-Git-Plugin, or perhaps jenkins-job-builder's abstraction for its parameters omits it, or perhaps we're just using it wrong.
Do you have an example or are you merely suspecting it is not using --init? The workspaces are usually wiped out (except for mediawiki-core jobs), so if Jenkins was failling to fetch the submodules we would have a ton of jobs failling. https://integration.wikimedia.org/ci/job/operations-puppet-doc/? does fetch submodules :)
Assuming this works for us since there are no examples.