Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42947

Bitbucket-branch-source plugin does not support GIT submodules

    XMLWordPrintable

Details

    Description

      In case of gitSCMSource we can define submodule policies for the branch:

       

      submoduleOption {
 disableSubmodules(false)
 recursiveSubmodules(true)
 parentCredentials(true)
 trackingSubmodules(false)
 reference("")
 timeout(1)
}

      bitbucketSCMSource does not support that so it's literally impossible to get things working without dirty hacks, like using sh("git submodule update --init"). Also it does require additional configuration of the target host, which is a completely bad thing.

       

      Related: 

      1. JENKINS-32658
      2. JENKINS-37658

      Attachments

        Issue Links

          duplicates

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-43507 Allow SCMSource and SCMNavigator subtypes to share common traits

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-37658 Github-branch-source plugin should support git plugin extensions

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            jordanlc Jordan Coll added a comment -

            I think this issue should be generalized for all advanced SCM behavior (clean/wipe workspace, reference repos, shallow clone, etc.)

            jordanlc Jordan Coll added a comment - I think this issue should be generalized for all advanced SCM behavior (clean/wipe workspace, reference repos, shallow clone, etc.)
            nfalco Nikolas Falco added a comment -

            I agree with jordanlc.
            We have the same needs for "clean after checkout", a lot of times I have to wipe out the workspace by hand connecting ssh to the jenkins node. I can not use GitPlugin in multibranch becuase this plugin is not able to restrict branches master and feature/*

            This is a big deal.

            nfalco Nikolas Falco added a comment - I agree with jordanlc . We have the same needs for "clean after checkout", a lot of times I have to wipe out the workspace by hand connecting ssh to the jenkins node. I can not use GitPlugin in multibranch becuase this plugin is not able to restrict branches master and feature/* This is a big deal.
            stephenconnolly Stephen Connolly added a comment -

            Now fixed by the changes in JENKINS-43507

            stephenconnolly Stephen Connolly added a comment - Now fixed by the changes in JENKINS-43507

            People

              amuniz Antonio Muñiz
              pshirshov P S
              Votes:
              11 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: