blocks|key|263251|text|在某个地方，我读到了一个组织，他们将大多数标准管道放入全面的共享库中。关于这一点，这篇文章是个不错的读物。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|263252|我自己的公司使用"Seedjobs“来创建多个只有一个作业的管道。请阅读这篇文章获得关于该想法的概述。|263253|entityMap|0|LINK|mutability|MUTABLE|url|https://jenkins.io/blog/2017/06/27/speaker-blog-SAS-jenkins-world/|1|https://docs.mesosphere.com/services/jenkins/3.5.4-2.150.1/script-template-job-dsl/^0|15|4|0|0|10|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Somewhere I read about an organization where they put most standard pipelines into comprehensive shared libraries. <a href="https://jenkins.io/blog/2017/06/27/speaker-blog-SAS-jenkins-world/" rel="nofollow noreferrer" title="This article">This article</a> is quite a good read about that.

My own company uses "Seedjobs" to create multiple pipelines with only one job. Read <a href="https://docs.mesosphere.com/services/jenkins/3.5.4-2.150.1/script-template-job-dsl/" rel="nofollow noreferrer">this article</a> for an overview on that idea.

blocks|key|1744064|text|我们通过创建Jenkins构建模板和根据该模板为每个url配置每个作业实现了这一目标。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1744065|我们可以有一个配置参数的作业，但是没有采用这种方法，因为这并不容易知道它是针对哪个git回购失败的，因为我们需要遍历每个构建的参数。|1744066|可以使用以下插件https://wiki.jenkins.io/display/JENKINS/Template%2BProject%2BPlugin创建模板|offset|length|1744067|entityMap|0|LINK|mutability|MUTABLE|url|http://Template%2520Project%2520plugin^0|0|0|8|1R|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

We had achieved it through creating Jenkins build templates and configuring each job for each url based on this template

We can have one job configured with parameters, but didn't go for that approach as that is not that easy to know for which git repo it is failing as we need to go through parameters of each build

Templates can be created using the following plugin <a href="http://Template%20Project%20plugin" rel="nofollow noreferrer">https://wiki.jenkins.io/display/JENKINS/Template+Project+Plugin</a>

blocks|key|263267|text|在做了更多的研究之后，我想我会尝试一下"GitHub+Organization“的工作类型。它扫描所有存储库以查找给定的GitHub组织或所有者，并自动管理相应的作业。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|263268|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

After having done a bit more research I think I will try the "GitHub Organization" job type. It scans all repositories for a given GitHub organization or owner and automatically manages corresponding jobs.

blocks|key|262457|text|我知道这个问题已经得到解答，但是还有一种简单的方法可以从多个GitHub+URL触发单个作业。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|262458|您可以使用通用Web钩子触发器插件从不同的GitHub存储库构建相同的作业。您需要为作业分配唯一的令牌，并将多个GitHub存储库的Web钩子配置为：|offset|length|262459|JENKINS_URL/generic-webhook-trigger/invoke?token=TOKEN_NAME|blockquote|262460|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jenkinsci/generic-webhook-trigger-plugin^0|0|5|C|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

I know this question is already answered, but there is another simple way of triggering a single Job from multiple GitHub URLs.
You could use <a href="https://github.com/jenkinsci/generic-webhook-trigger-plugin" rel="nofollow noreferrer">Generic Webhook Trigger Plugin</a> to build same Job from different GitHub repositories. You need to assign unique token to the Job and configure the Webhook of multiple GitHub repositories as:
<blockquote>
JENKINS_URL/generic-webhook-trigger/invoke?token=TOKEN_NAME
</blockquote>

I have a very simple Jenkins build which is needed for several repositories. All these repositories have the same organisation, the same branches, etc. There is no difference except the repository name.

Each single repository should be able to trigger the build for only this specific repository. I imagine something like combining a <a href="https://wiki.jenkins.io/display/JENKINS/Parameterized+Build" rel="noreferrer">parameterized build</a> with a WebHook URL containing a query parameter for the repository name maybe.

Any ideas or pointers about that?

Reuse one Jenkins jobs for multiple Git (GitHub) repositories

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个非常简单的Jenkins构建，这是几个存储库所需要的。所有这些存储库都有相同的组织，相同的分支，等等。除了存储库的名称之外，没有什么不同。每个存储库都应该能够只为这个特定的存储库触发构建。我设想可能是将与包含存储库名称的查询参数的WebHook URL组合起来。对此有什么想法或建议吗？

问为多个Git (GitHub)存储库重用一个Jenkins作业
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为多个Git (GitHub)存储库重用一个Jenkins作业EN