jenkins管道和git继续建设

Question

我有一个完美的管道，直到两天前运行。它被配置为从* / master从Git获取Jenkins文件。 在不对作业配置进行任何更改或升级任何插件的情况下，作业开始不断构建。

到目前为止，我已尝试过以下内容：

1. 将分支从* / master更改为refs / heads / master
2. 创建一个与原始作业相同的新作业
3. Jenkins文件已从声明式更改为脚本式，我还原了它仍然触发
4. 我已升级到最新的Jenkins（2.73.2）并升级了所有插件
5. 为同一个项目创建一个自由式作业，但不会触发
6. 删除了已使用的共享库，仍触发

如果您有任何提示，请告诉我

这是freestle项目的轮询日志     Git Polling Log

Started on Oct 15, 2017 9:20:00 PM
Using strategy: Default
[poll] Last Built Revision: Revision 8a68578bf81dba01bd00e2c83981cde69933ece9 (refs/remotes/origin/master)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://server:29418/DEPT/project # timeout=10
Found 11 remote heads on ssh://server:29418/DEPT/project
[poll] Latest remote head revision on refs/heads/master is: 8a68578bf81dba01bd00e2c83981cde69933ece9 - already built by 2
Done. Took 63 ms
No changes

这是继续触发的作业的轮询日志：

Started on Oct 15, 2017 9:19:00 PM
Using strategy: Default
[poll] Last Built Revision: Revision 4d210e24c65cefe2104c1629ca6954d5eb863b04 (origin/test-build-issue)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://server:29418/DEPT/project # timeout=10
Found 11 remote heads on ssh://server:29418/DEPT/project
[poll] Latest remote head revision on refs/heads/test-build-issue is: 4d210e24c65cefe2104c1629ca6954d5eb863b04 - already built by 11
RTC : checking for changes...
Using strategy: Default
[poll] Last Built Revision: Revision 4d210e24c65cefe2104c1629ca6954d5eb863b04 (origin/test-build-issue)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://server:29418/DEPT/project # timeout=10
Found 11 remote heads on ssh://server:29418/DEPT/project
[poll] Latest remote head revision on refs/heads/test-build-issue is: 4d210e24c65cefe2104c1629ca6954d5eb863b04 - already built by 11
Using strategy: Default
[poll] Last Built Revision: Revision 4d210e24c65cefe2104c1629ca6954d5eb863b04 (origin/test-build-issue)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://server:29418/DEPT/project # timeout=10
Found 11 remote heads on ssh://server:29418/DEPT/project
[poll] Latest remote head revision on refs/heads/test-build-issue is: 4d210e24c65cefe2104c1629ca6954d5eb863b04 - already built by 11
Using strategy: Default
[poll] Last Built Revision: Revision 4d210e24c65cefe2104c1629ca6954d5eb863b04 (origin/test-build-issue)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://server:29418/DEPT/project # timeout=10
Found 11 remote heads on ssh://server:29418/DEPT/project
[poll] Latest remote head revision on refs/heads/test-build-issue is: 4d210e24c65cefe2104c1629ca6954d5eb863b04 - already built by 11
Using strategy: Default
[poll] Last Built Revision: Revision 4d210e24c65cefe2104c1629ca6954d5eb863b04 (origin/test-build-issue)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://server:29418/DEPT/project # timeout=10
Found 11 remote heads on ssh://server:29418/DEPT/project
[poll] Latest remote head revision on refs/heads/test-build-issue is: 4d210e24c65cefe2104c1629ca6954d5eb863b04 - already built by 11
Using strategy: Default
[poll] Last Built Revision: Revision 4d210e24c65cefe2104c1629ca6954d5eb863b04 (origin/test-build-issue)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://server:29418/DEPT/project # timeout=10
Found 11 remote heads on ssh://server:29418/DEPT/project
[poll] Latest remote head revision on refs/heads/test-build-issue is: 4d210e24c65cefe2104c1629ca6954d5eb863b04 - already built by 11
Done. Took 0.66 sec
Changes found