--- jobs/linaro-android_panda/config.xml 2011-08-29 16:30:58 +0000 +++ jobs/linaro-android_panda/config.xml 2011-09-15 09:30:39 +0000 @@ -49,9 +50,8 @@ <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding> <triggers class="vector"> <hudson.triggers.TimerTrigger> - <spec>0 2 * * *</spec> - </hudson.triggers.TimerTrigger> - </triggers> + <spec>@daily</spec> + </hudson.triggers.TimerTrigger></triggers> <concurrentBuild>true</concurrentBuild> <builders> <hudson.tasks.Shell>
So, as seen from the above, there used to be time-interleave setting made (manually) by yours truly. But people click buttons [without need], and carefully crafted settings get reset. Conclusion: we need to automate this interleave settings.
--- jobs/linaro- android_ panda/config. xml 2011-08-29 16:30:58 +0000 android_ panda/config. xml 2011-09-15 09:30:39 +0000 henUpstreamBuil ding>false< /blockBuildWhen UpstreamBuildin g> triggers. TimerTrigger> triggers. TimerTrigger> triggers. TimerTrigger> </triggers> uild>true< /concurrentBuil d> tasks.Shell>
+++ jobs/linaro-
@@ -49,9 +50,8 @@
<blockBuildW
<triggers class="vector">
<hudson.
- <spec>0 2 * * *</spec>
- </hudson.
- </triggers>
+ <spec>@daily</spec>
+ </hudson.
<concurrentB
<builders>
<hudson.
So, as seen from the above, there used to be time-interleave setting made (manually) by yours truly. But people click buttons [without need], and carefully crafted settings get reset. Conclusion: we need to automate this interleave settings.