发出拉取请求后,Jenkins禁用分支上的项目构建 [英] Jenkins disables project builds on branches after a pull request is issued

查看:66
本文介绍了发出拉取请求后,Jenkins禁用分支上的项目构建的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

注意:我仅在我的一个分支中设置了Jenkinsfile,而不在主分支中设置.

Note: I only have Jenkinsfile set up in one of my branches, not the master.

我已经设置了Git Webhooks来监视推送到我的Github存储库的事件.但是,我注意到我的Jenkins版本作为分支正常运行(拾取推送事件,触发版本),但是在发出拉取请求后,我的分支版本在 Branches 选项卡中被禁用我的项目.

I have setup Git webhooks to monitor push events to my Github repository. However, I am noticing that my Jenkins builds are working fine (picking up push events, triggering builds) as branches, but after a pull request is issued, my branch build gets disabled in the Branches tab of my project.

但是,我确实在 Pull Requests 标签中看到了新的PR.但是现在,当我使用Github时,新提交不再触发构建.在我的分支选项卡中,我的旧分支现在被划掉了.

However, I do see the new PR listed in my Pull Requests tab. But now, when I push to Github, the new commits are not triggering builds anymore. In my branches tab, my old branch is now crossed out.

如何迫使詹金斯继续建立分支机构?即使发布了PR,我也希望继续从分支机构进行构建.

推荐答案

这是因为您对该分支具有正在进行的PR,只要PR达到任何最终状态,您的禁用分支都将再次启用.

That's because you have an on going PR for that branch, whenever the PR reaches any final status, your disabled branch will be enabled again.

这篇关于发出拉取请求后,Jenkins禁用分支上的项目构建的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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