Job Not Triggering after Being Re-Enabled

23 views
Skip to first unread message

Nick Lee

unread,
Oct 13, 2015, 12:41:09 PM10/13/15
to Jenkins Users
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").

Baptiste Mathus

unread,
Oct 13, 2015, 3:54:07 PM10/13/15
to jenkins...@googlegroups.com
Hi,
With seemingly bugs, it's generally better to provide your relevant environment informations: jenkins & plugin versions, OS... 
Is there anything about it in the logs when you reenable/before?
Thanks

--
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-use...@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.



--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Nick Lee

unread,
Oct 13, 2015, 4:05:05 PM10/13/15
to jenkins...@googlegroups.com
I'm currently running Jenkins 1.630, running under Windows 8. I have the following plugins installed:

Active Directory plugin 1.41
Ant Plugin 1.2
Artifact Deployer Plug-in 0.33
Authorize Project 1.1.0
CloudBees Build Flow plugin 0.18
conditional-buildstep 1.3.3
Configuration Slicing plugin 1.44
Copy Artifact Plugin 1.36.1
Credentials Plugin 1.23
CVS Plug-in 2.12
Email Extension Plugin 2.40.5
Environment Injector Plugin 1.92.1
External Monitor Job Type Plugin 1.4
GIT client plugin 1.19.0
Groovy 1.27
Groovy Label Assignment plugin 1.1.1
Groovy Postbuild 2.2.1
Javadoc Plugin 1.3
jQuery plugin 1.11.2-0
JUnit Plugin 1.9
LDAP Plugin 1.11
Lockable Resources plugin 1.7
Mailer Plugin 1.15
MapDB API Plugin 1.0.6.0
Matrix Authorization Strategy Plugin 1.2
Matrix Project Plugin 1.6
Maven Integration plugin 2.12.1
Monitoring 1.57.0
Multijob plugin 1.18
Node and Label parameter plugin 1.5.1
OWASP Markup Formatter Plugin 1.3
PAM Authentication plugin 1.2
Parameterized Trigger plugin 2.29
Perforce Plugin 1.3.35
ruby-runtime 0.12
Run Condition Plugin 1.0
SCM API Plugin 0.2
Script Security Plugin 1.15
SSH Credentials Plugin 1.11
SSH Slaves plugin 1.10
Subversion Plug-in 2.5.3
Throttle Concurrent Builds Plug-in 1.8.4
Token Macro Plugin 1.10
Translation Assistance plugin 1.12
Windows Slaves Plugin 1.1
Workspace Cleanup Plugin 0.28

I don't see any obvious issues in the Jenkins system log. Is there another log that I should be looking at?

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/es6aImyGdrY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5VcE5xa%2BZPHvMqSrjayK8-MF0-8uiDypkYJ%3DHCc938ZQ%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages