Project

General

Profile

Actions

Bug #4913

closed

jenkins-job-builder silently discards git clone 'recursive' setting for sub-modules

Added by laforge over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
12/17/2020
Due date:
% Done:

100%

Spec Reference:

Description

I followed the example at https://github.com/OSSystems/jenkins-job-builder/blob/master/tests/scm/fixtures/git-submodule01.yaml when writing https://gerrit.osmocom.org/c/osmo-ci/+/21764 but the generated job e.g. https://jenkins.osmocom.org/jenkins/search/?q=master-osmo-e1-hardware does not actually have the "Additional Behaviours" -> "Advanced sub-modules behaviours" -> "Recursively update submodules" set. I had to manually add this, but that of course gets overwritten every time soemebody re-deploys the jobs.

Any ideas, lynxis?

Actions #1

Updated by laforge over 3 years ago

basically the following block is missing:

    <extensions>
      <hudson.plugins.git.extensions.impl.SubmoduleOption>
        <disableSubmodules>false</disableSubmodules>
        <recursiveSubmodules>true</recursiveSubmodules>
        <trackingSubmodules>false</trackingSubmodules>
        <reference></reference>
        <parentCredentials>false</parentCredentials>
        <shallow>false</shallow>
      </hudson.plugins.git.extensions.impl.SubmoduleOption>
    </extensions>
Actions #2

Updated by laforge over 3 years ago

  • Status changed from New to Resolved
  • Assignee changed from lynxis to laforge
  • % Done changed from 0 to 100

moving the options into the job template resolved the issue.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)