Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
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:
Attachments
Issue Links
- duplicates
-
JENKINS-43507 Allow SCMSource and SCMNavigator subtypes to share common traits
-
- Resolved
-
- relates to
-
JENKINS-37658 Github-branch-source plugin should support git plugin extensions
-
- Closed
-
Activity
P S
created issue -
P S
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | Bitbiclet-branch-source plugin does not support GIT submodules | Bitbucket-branch-source plugin does not support GIT submodules |
P S
made changes -
| Description |
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. |
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: # |
P S
made changes -
| Description |
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: # |
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: # - # |
| Link |
This issue relates to |
| 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.* ] |
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.
| Link |
This issue duplicates |
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
I think this issue should be generalized for all advanced SCM behavior (clean/wipe workspace, reference repos, shallow clone, etc.)