I have a job that uses a periodic build trigger. I've set the trigger to 
"H/10 * * * *" -- basically, build every ten minutes.

Now this works perfectly fine most of the time. However, if I disable the 
job for a long period of time (say, 30 minutes), then re-enable it, the 
build trigger won't restart automatically, no matter how long I wait. I 
have to manually open the job configuration page, hit the "Save" button, 
and only then will the periodic trigger work again.

It seems like whatever timing mechanism Jenkins uses doesn't get reset on 
job re-enable for some reason, and will only reset if the job configuration 
is actually re-saved. Is this a bug? Is there a fix or reliable workaround 
to this problem? I want our Jenkins users to be able to disable/enable jobs 
easily without having to go to the trouble of manually saving the job 
configuration each time (a process which may introduce bugs if someone 
accidentally changes a configuration setting before pressing "save").

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/226dd02a-e570-439c-904c-a9b2b0caef2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to