在Jenkins中构建多个Azure DevOps Pull请求 [英] Build Multi Azure DevOps Pull Request in Jenkins

查看:107
本文介绍了在Jenkins中构建多个Azure DevOps Pull请求的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的git存储库是Azure Dev-Ops,使用Jenkins进行持续集成构建,而我使用tfs Plugin for Jenkins.
我的代码有6个分支:

My git repository is Azure Dev-Ops and use Jenkins for continuous integration build and I use tfs Plugin for Jenkins.
My code has 6 branches:

master,test1,test2,test3,test4,test5

master, test1, test2, test3, test4, test5

当我想要拉取请求test1 to master(例如拉取请求号为100)和test5 to test4(例如拉取请求号为101)时,Jenkins仅构建号为100的拉取请求,而不构建拉号101.

When i want pull request test1 to master(for example pull request number is 100) and test5 to test4(for example pull request number is 101) Jenkins only build pull request for number 100 don't build pull request number 101.

几次后,当我要为请求请求构建test3 to test2(例如,请求请求编号为102)时,詹金斯再次为请求请求构建100.

after several time when i want build for pull request test3 to test2(for example pull request number is 102) Jenkins again build for pull request number 100.

我不知道怎么了.

推荐答案

我对Service的理解钩住了Jenkins服务的Azure Dev-ops 我们有2个触发条件

I Understood in Service hooks Azure Dev-ops for Jenkins service we have 2 trigger that are

  1. 触发通用构建
  2. 触发Git构建

不幸的是,

在tfs的官方文档中https://github.com/jenkinsci/tfs-plugin并没有说Trigger generic build用于只有一个分支的情况,而Trigger Git Build用于我们在管道Jenkins上有多个分支的情况. 所以我将触发器从Trigger generic build更改为Trigger Git Build

unfortunately in official document for tfs https://github.com/jenkinsci/tfs-plugin don't say that Trigger generic build use for when we have only a branch and Trigger Git Build use for when we have multi branch on pipeline Jenkins. So I change my trigger from Trigger generic build to Trigger Git Build

这篇关于在Jenkins中构建多个Azure DevOps Pull请求的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆