詹金斯将保持在构建队列作业，并保持他们建设 [英] Jenkins keeps adding job in the build queue and keeps building them

问题描述

我们使用詹金斯使用Git，所有的作业都配置为，每一个有承诺的Git，清洁的工作区和触发生成时间。这种情况下工作正常。

We use Jenkins with Git, and all the jobs are configured as, every time there is commit to Git, clean the workspace and trigger a build. This scenario is working fine.

现在的情况是，不知道确切的原因，但可能会在重启系统，所有的工作不断得到添加到构建队列就像一个无限循环，然后开始工作失败。
（工作时分别触发，他们去成功）

Now the situation is, don't know the exact reason why but may be on restart of the system, all the jobs keeps on getting added to the build queue like an infinite loop, then jobs starts failing. (When jobs are triggered separately, they goes successful)

什么可以为上述做了什么？
我已经给人头SCM的 * 的*，使其尽快，因为它已提交需要从混帐的变化，可以在有问题？

what can be done for the above? I have given "POLL SCM **" so that it takes the change from the git as soon as it has a commit, can that be a problem?

推荐答案

我只是碰到这种循环效应的詹金斯今晚来构建。我运行詹金斯1.598的最新版本，并使用GIT插件2.3.4的最新版本。

I just came across this looping effect of Builds in Jenkins tonight. I'm running the current version of Jenkins 1.598 and using the current version of GIT plugin 2.3.4.

的设置都发生了变化，除了加入令牌的GIT URL文本框内的HTTPS。我有第一个构建成功完成后运行一个不同的生成一个构建后选项。我有这些类型的4共建立是8建立在总。节能设置所有的标记修改之后，然后我跑了4同时建立。这就是循环开始了。

None of the settings have changed except for adding a token to the https within the GIT URL textfields. I have a build-after option that runs a different build after the first build is successfully completed. I have 4 of these types of builds altogether which is 8 builds in total. After saving settings for all of the token changes, I then ran the 4 builds simultaneously. This is where the looping began.

我开始注意到，第一个构建将完成并引发二次生成后。一旦次级建立后完成的，神秘的第4构建出了在排队。
我还相信，我没有任何其他的集结后设置在二级建造指向第一的基础之上。

I started noticing that the first builds would finish and trigger the secondary after-builds. Once the secondary after-builds completed, mysteriously the first 4 builds were showing up in the queue. I also made sure that I did not have any other build-after setups in the secondary builds pointing to the first builds.

所以，于我而言，似乎仍然存在与最新版本的这个循环的问题也是如此。

So, in my case, it seems that there is still this looping issue with the most current versions as well.

解决方案：
正如丹·伍德沃德指出，在重新启动该服务詹金斯实例为我们的微软操作系统的服务器解决了这个问题。我的直觉是，每一个改变之后，它可能是一个好主意，重新启动詹金斯即使这是不是从詹金斯的要求。但是，它可能会解决任何可能的问题，如这个循环的bug。

SOLUTION: As Dan Woodward pointed out, restarting the Jenkins instance in Services for our Microsoft OS server solved the issue. My hunch is that after every setting change, it is probably a good idea to restart Jenkins even though this is not a requirement from Jenkins. However, it could potentially resolve any possible issues such as this looping bug.

这篇关于詹金斯将保持在构建队列作业，并保持他们建设的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！