简体繁体 English

Jenkins 来自版本控制 (Bitbucket) 的多分支管道 - 我可以为特定分支指定规则吗？

[英]Jenkins Multibranch Pipeline from Version Control (Bitbucket) - can I specify rules for specific branches?

原文 2019-11-05 09:21:05 2 1 jenkins/ jenkins-pipeline/ bitbucket/ multibranch-pipeline

I am currently creating a multibranch pipeline from BitBucket, which will build all branches automatically.我目前正在从 BitBucket 创建一个多分支管道，它将自动构建所有分支。 That would be extremely helpful for pull requests and overall save a lot of time.这对于拉取请求非常有帮助，并且总体上可以节省大量时间。 However this specific project is a little bit different - it is a web application and it is built with 2 different Jenkins jobs:然而，这个特定的项目有点不同 - 它是一个 web 应用程序，它由 2 个不同的 Jenkins 作业构建：

Job 1: Checkout files from Version Control (Subversion and Git) and if successfull trigger Job 2 (from the job configuration).作业 1：从版本控制（Subversion 和 Git）签出文件，如果成功触发作业 2（从作业配置）。

Job 2: Transfer the files from Job 1 to node, and execute the deployment scripts.作业 2：将作业 1 中的文件传输到节点，并执行部署脚本。 There is a lot of extra configuration in the job, which I do not need to explain.工作中有很多额外的配置，我不需要解释。 If this job is successful, the web application is deployed.如果此作业成功，则部署 web 应用程序。

However, how the multibranch pipeline works is that it points to the Jenkinsfile of each branch (which starts Job 1) and builds that.但是，多分支管道的工作方式是它指向每个分支的 Jenkinsfile（它启动 Job 1）并构建它。 Everytime is successful, however it doesn't trigger Job 2. Also in BitBucket it shows up as successfull build for all branches, because it only looks for this specific job.每次都成功，但它不会触发作业 2。同样在 BitBucket 中，它显示为所有分支的成功构建，因为它只查找此特定作业。

Is there a way I can make individual rules for the branch jobs, so that they trigger another job, and that BitBucket looks for that job as a reference if a build has passed or failed?有没有办法可以为分支作业制定单独的规则，以便它们触发另一个作业，如果构建通过或失败，BitBucket 会查找该作业作为参考？ I would very much not like to combine the whole functionality in a single JenkinsFile, because it would be a massive change.我非常不想将整个功能组合在一个 JenkinsFile 中，因为这将是一个巨大的变化。 Thank you.谢谢你。

1 个解决方案

It is not clear what actions you do in your second Job to understand if it is common for all the jobs or it is very different for each branch.目前尚不清楚您在第二份工作中执行了哪些操作，以了解是所有工作都通用还是每个分支都非常不同。

First with the assumption, your second job is common for all the branches, you can have a Jenkins file in each branch which triggers the common job (based on another jenkins file which is in a common location) in it.首先假设，您的第二个工作对所有分支都是通用的，您可以在每个分支中有一个 Jenkins 文件，该文件会触发公共工作（基于另一个位于公共位置的 jenkins 文件）。

Second, if the functionality is different for each branch, what I would suggest is come up with a generic functions and try passing parameters based on the requirement of each branch in the first Jenkins file.其次，如果每个分支的功能不同，我建议提出一个通用函数，并尝试根据第一个 Jenkins 文件中每个分支的要求传递参数。

This is just an idea.这只是一个想法。 If you can explain little bit more about the second jobs behaviour, I might be able to throw some more ideas to help you.如果你能解释更多关于第二份工作的行为，我可能会提出更多的想法来帮助你。