blocks|key|5880546|text|使用sh+'git+submodule...'的解决方案只适用于没有特殊身份验证的存储库。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5880547|我们在设置中使用以下解决方案：|5880548|node+{
++++checkout([
++++++++$class:+'GitSCM',
++++++++branches:+scm.branches,
++++++++doGenerateSubmoduleConfigurations:+true,
++++++++extensions:+scm.extensions+%2B+[[$class:+'SubmoduleOption',+parentCredentials:+true]],
++++++++userRemoteConfigs:+scm.userRemoteConfigs
++++])
}|code-block|syntax|javascript|5880549|entityMap^0|2|L|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

The solution with <code>sh 'git submodule...'</code> works only for Repositorys without special authentication.

We use following solution in our set up:

<pre><code>node {
 checkout([
 $class: 'GitSCM',
 branches: scm.branches,
 doGenerateSubmoduleConfigurations: true,
 extensions: scm.extensions + [[$class: 'SubmoduleOption', parentCredentials: true]],
 userRemoteConfigs: scm.userRemoteConfigs
 ])
}
</code></pre>

blocks|key|5880591|text|在Github组织插件中，添加高级子模块行为。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5880592|​|5880593|📷|atomic|offset|length|5880594|5880595|并将其配置如下：|5880596|5880597|5880598|5880599|5880600|正如@oeuftete所指出的，如果子模块使用SSH协议，您可能还需要添加"Checkout+over+SSH“行为(并提供密钥凭证)。|5880601|如下所示：https://wiki.jenkins.io/display/JENKINS/Git%2BPlugin|5880602|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6d5b1f2806262be4fd54abbe815c0d3c.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/0084d3c1ef90056b4e0c8a98c70dce02.png|2|LINK|MUTABLE|url|https://wiki.jenkins.io/display/JENKINS/Git%2BPlugin^0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0|5|1E|2|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1B|8|@]|9|@$G|1C|H|1D|1|1E]]|A|$]]|$1|I|3|C|5|6|7|1F|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@]|9|@]|A|$]]|$1|L|3|C|5|6|7|1H|8|@]|9|@]|A|$]]|$1|M|3|E|5|F|7|1I|8|@]|9|@$G|1J|H|1K|1|1L]]|A|$]]|$1|N|3|C|5|6|7|1M|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1O|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1P|8|@]|9|@$G|1Q|H|1R|1|1S]]|A|$]]|$1|T|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10|11|-4]]|12|$5|W|X|Y|A|$Z|13|11|-4]]|14|$5|15|X|16|A|$17|18]]]]

In the Github organization plugin, add the advanced submodule behaviors.

<a href="https://i.stack.imgur.com/Amlif.png" rel="noreferrer"><img src="https://i.stack.imgur.com/Amlif.png" alt="Org Setings Page"></a>

And configure it like this:

<a href="https://i.stack.imgur.com/vp0aX.png" rel="noreferrer"><img src="https://i.stack.imgur.com/vp0aX.png" alt="enter image description here"></a>

<hr>

As @oeuftete pointed out, you also may need to add the "Checkout over SSH" behaviour (and provide a key credential) if the submodule(s) use the SSH protocol.

As documented here: <a href="https://wiki.jenkins.io/display/JENKINS/Git+Plugin" rel="noreferrer">https://wiki.jenkins.io/display/JENKINS/Git+Plugin</a>

blocks|key|1796736|text|将其更改为：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1796737|node+{
++++checkout+scm
++++sh+'git+submodule+update+--init'
}|code-block|syntax|javascript|1796738|如果Jenkins在Windows上运行，请使用bat而不是sh。|offset|length|style|CODE|1796739|entityMap^0|0|0|O|3|U|2|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

Change it to this:

<pre><code>node {
 checkout scm
 sh 'git submodule update --init'
}
</code></pre>

Use <code>bat</code> instead of <code>sh</code> if Jenkins is running on Windows.

blocks|key|2352489|text|我们有类似的问题，Jenkin用户正在使用https从Github拉取，但是子模块使用SSH，我们希望使用Jenkins处理拉取请求。我做了下面的结账阶段，希望能对这里的人有所帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2352490|stage('Checkout')+{
++if(env.BRANCH_NAME+==+"develop"+%7C%7C+env.BRANCH_NAME+==+"master")+{
++++checkout([
++++++$class:+'GitSCM',
++++++branches:+scm.branches,
++++++doGenerateSubmoduleConfigurations:+false,
++++++extensions:+[[$class:+'SubmoduleOption',
++++++++++++++++++++disableSubmodules:+false,
++++++++++++++++++++parentCredentials:+true,
++++++++++++++++++++recursiveSubmodules:+true,
++++++++++++++++++++reference:+'',
++++++++++++++++++++trackingSubmodules:+false],
+++++++++++++++++++[$class:+'CleanBeforeCheckout'],+
+++++++++++++++++++[$class:+'CleanCheckout']],
++++++submoduleCfg:+[],
++++++userRemoteConfigs:+[[credentialsId:+'jenkins-ssh',
+++++++++++++++++++++++++++url:+'git@github.com:<AccountName>/<RepoName.git>']]
++++++++++++++++++++++++++])
++}
++else+if+(env.CHANGE_ID)+{
++++checkout([
++++++$class:+'GitSCM',
++++++branches:+[[name:+"FETCH_HEAD"]],
++++++doGenerateSubmoduleConfigurations:+false,
++++++extensions:+[[$class:+'SubmoduleOption',
++++++++++++++++++++disableSubmodules:+false,
++++++++++++++++++++parentCredentials:+true,
++++++++++++++++++++recursiveSubmodules:+true,
++++++++++++++++++++reference:+'',
++++++++++++++++++++trackingSubmodules:+false],
+++++++++++++++++++[$class:+'CleanBeforeCheckout'],+
+++++++++++++++++++[$class:+'CleanCheckout']],
++++++submoduleCfg:+[],
++++++userRemoteConfigs:+[[credentialsId:+'jenkins-ssh',+
+++++++++++++++++++++++++++refspec:+"%2Brefs/pull/${CHANGE_ID}/head:refs/remotes/origin/${BRANCH_NAME}+%2Brefs/heads/${CHANGE_TARGET}:refs/remotes/origin/${CHANGE_TARGET}",+
+++++++++++++++++++++++++++url:+'git@github.com:<AccountName>/<RepoName.git>']]
++++])
++}
}|code-block|syntax|javascript|2352491|也许有一种更简单的方法，我很高兴听到你的消息:-)|2352492|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

We had similar issue, Jenkin user is using https to pull from Github but the submodule is using SSH and we want to handle the pull requests with Jenkins.
I did the below checkout stage hope it will help someone here:

<pre><code>stage('Checkout') {
 if(env.BRANCH_NAME == "develop" || env.BRANCH_NAME == "master") {
 checkout([
 $class: 'GitSCM',
 branches: scm.branches,
 doGenerateSubmoduleConfigurations: false,
 extensions: [[$class: 'SubmoduleOption',
 disableSubmodules: false,
 parentCredentials: true,
 recursiveSubmodules: true,
 reference: '',
 trackingSubmodules: false],
 [$class: 'CleanBeforeCheckout'], 
 [$class: 'CleanCheckout']],
 submoduleCfg: [],
 userRemoteConfigs: [[credentialsId: 'jenkins-ssh',
 url: 'git@github.com:&lt;AccountName&gt;/&lt;RepoName.git&gt;']]
 ])
 }
 else if (env.CHANGE_ID) {
 checkout([
 $class: 'GitSCM',
 branches: [[name: "FETCH_HEAD"]],
 doGenerateSubmoduleConfigurations: false,
 extensions: [[$class: 'SubmoduleOption',
 disableSubmodules: false,
 parentCredentials: true,
 recursiveSubmodules: true,
 reference: '',
 trackingSubmodules: false],
 [$class: 'CleanBeforeCheckout'], 
 [$class: 'CleanCheckout']],
 submoduleCfg: [],
 userRemoteConfigs: [[credentialsId: 'jenkins-ssh', 
 refspec: "+refs/pull/${CHANGE_ID}/head:refs/remotes/origin/${BRANCH_NAME} +refs/heads/${CHANGE_TARGET}:refs/remotes/origin/${CHANGE_TARGET}", 
 url: 'git@github.com:&lt;AccountName&gt;/&lt;RepoName.git&gt;']]
 ])
 }
}
</code></pre>

Maybe there is an easier way to do it, I would be happy to hear from you :-)

I have a build job in Jenkins created by the <a href="https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Organization+Folder+Plugin" rel="noreferrer">Github Organization plugin</a>. The <code>Jenkinsfile</code> for this build checkouts the code using <code>checkout scm</code> which is good as it figures out the correct branch/revision to checkout when building either PR triggered changes or pushes to the master branch. 

How can I make this: 

<pre><code>node {
 checkout scm 
}
</code></pre>

checkout submodules?

Checkout submodules in Jenkins with Github organisation plugin

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

我在创建的Jenkins中有一个构建工作。此构建的Jenkinsfile使用checkout scm签出代码，这很好，因为当构建PR触发更改或推送到主分支时，它会找出要签出的正确分支/修订。我该怎么做：node {  checkout scm }检出子模块？

问Jenkins中使用Github组织插件的签出子模块
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins中使用Github组织插件的签出子模块EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins中使用Github组织插件的签出子模块
EN