詹金斯管道和git继续建设

直到两天前，我已经有了一条完美的管道。它被配置为从*/master获取Git中的Jenkins文件。 在不更改作业配置或升级任何插件的情况下，作业开始持续构建

到目前为止，我尝试了以下方法：

将分支从*/master更改为refs/heads/master

创建与原始作业相同的新作业

Jenkins文件已从声明式更改为脚本式，我对此进行了恢复，它仍然会触发

我已经升级到最新的Jenkins（2.73.2）并升级了所有插件

为同一项目创建自由式作业，这不会触发

已删除已使用的共享库，但仍会触发

如果你有什么建议，请告诉我

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

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

---

生成日志中的触发原因是什么？生成日志中没有报告任何更改控制台日志的第一行？用单片机构建触发器？是的，构建是由SCM更改触发的。然后，当您跟随链接时，它会显示上面的轮询日志。但是“更改”下的部分不存在。现在，当我将共享库从旧的SCM RTC移动到Git时，它看起来已经解决了。在这之后，现在看起来还不错。我猜RTC中的共享库存在问题，因为我将RTC用于其他项目，但没有问题。生成日志中的触发原因是什么？生成日志中没有报告任何更改控制台日志的第一行？用单片机构建触发器？是的，构建是由SCM更改触发的。然后，当您跟随链接时，它会显示上面的轮询日志。但是“更改”下的部分不存在。现在，当我将共享库从旧的SCM RTC移动到Git时，它看起来已经解决了。在这之后，现在看起来还不错。我的猜测是，RTC中的共享库存在问题，因为我将RTC用于其他项目，并且没有问题。