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

Bitbucket-branch-source plugin does not support GIT submodules

XMLWordPrintable

      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

          [JENKINS-42947] Bitbucket-branch-source plugin does not support GIT submodules

          P S created issue -
          P S made changes -
          Summary Original: Bitbiclet-branch-source plugin does not support GIT submodules New: Bitbucket-branch-source plugin does not support GIT submodules
          P S made changes -
          Description Original: In case of gitSCMSource we can define submodule policies for the branch:

           
          {code:java}
          submoduleOption {
           disableSubmodules(false)
           recursiveSubmodules(true)
           parentCredentials(true)
           trackingSubmodules(false)
           reference("")
           timeout(1)
          }{code}
          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.           		New: In case of gitSCMSource we can define submodule policies for the branch:

           
          {code:java}
          submoduleOption {
           disableSubmodules(false)
           recursiveSubmodules(true)
           parentCredentials(true)
           trackingSubmodules(false)
           reference("")
           timeout(1)
          }{code}
          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: 
           # JENKINS-32658
          P S made changes -
          Description Original: In case of gitSCMSource we can define submodule policies for the branch:

           
          {code:java}
          submoduleOption {
           disableSubmodules(false)
           recursiveSubmodules(true)
           parentCredentials(true)
           trackingSubmodules(false)
           reference("")
           timeout(1)
          }{code}
          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: 
           # JENKINS-32658           		New: In case of gitSCMSource we can define submodule policies for the branch:

           
          {code:java}
          submoduleOption {
           disableSubmodules(false)
           recursiveSubmodules(true)
           parentCredentials(true)
           trackingSubmodules(false)
           reference("")
           timeout(1)
          }{code}
          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: 
           # -JENKINS-32658-
           # JENKINS-37658
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-37658 [ JENKINS-37658 ]

          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.)

          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.)
          Nikolas Falco made changes -
          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.* ]

          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.

          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.

          Stephen Connolly added a comment -

          Now fixed by the changes in JENKINS-43507

          Stephen Connolly added a comment - Now fixed by the changes in JENKINS-43507
          Stephen Connolly made changes -
          Link New: This issue duplicates JENKINS-43507 [ JENKINS-43507 ]
          Stephen Connolly made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

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

              Created:
              Updated:
              Resolved: