为什么即使没有SVN改变,Jenkins也会触发IVY构建?

时间:2016-08-04 08:38:35

标签: svn jenkins ivy

我有一个Jenkins工作,每五分钟轮询一次SVN进行更改。我看到了奇怪的行为,即使日志清楚地表明自上次调查以来没有SCM变化。 Jenkins解析各个ivy.xml文件,并调用每个build.xml文件。然后构建文件编译已在Jenkins工作区中检出的代码,然后将1.0快照jar工件发布到IVY。这基本上是向IVY发布相同的快照。试图理解为什么Jenkins继续解析常春藤文件,即使没有检测到SCM更改。

作业的日志输出如下所示。

   Started by user anonymous
   [EnvInject] - Loading node environment variables.
   Building in workspace C:\Software\Jenkins\workspace\Snapshots
   Updating svn://*****/Project1 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   Updating svn://*****/Project2 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   Updating svn://*****/Project3 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   Updating svn://*****/Project4 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   Updating svn://*****/Project5 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   Updating svn://*****/Project6 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   Updating svn://*****/Project7 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   Updating svn://*****/Project8 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   Updating svn://*****/Project9 at revision '2016-08-04T09:04:38.318 +0100'
   At revision 3570
   no change for svn://*****/Project1 since the previous build
   no change for svn://*****/Project2 since the previous build
   no change for svn://*****/Project3 since the previous build
   no change for svn://*****/Project4 since the previous build
   no change for svn://*****/Project5 since the previous build
   no change for svn://*****/Project6 since the previous build
   no change for svn://*****/Project7 since the previous build
   no change for svn://*****/Project8 since the previous build
   no change for svn://*****/Project9 since the previous build
   Parsing Ivy Descriptor Files
   Triggering com.****:ivy1
   Triggering com.****:ivy2
   Triggering .....

   Finished: SUCCESS

欢迎任何指示。

1 个答案:

答案 0 :(得分:0)

用户启动“匿名” 您能否确认存在安全设置,并且不是每个人都能够手动触发构建。 “匿名”表示有人手动触发构建。