|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Apologies for the delay with any response. Busy with some deadlines.![]()
I am still seeing some oddities here. Our label updates every day and I am seeing the SCM Polling for the job fire off twice. Once, correctly when the label goes through. The second trigger is 10 minutes after the first, the time I have my SCM polling setup to go. The new polling log for the second job does show less CL's than the initial triggered job. I presume this is due to the trigger running while the job is busy syncing? I'll attach my two polling logs.
This is all this machine does is wait for the label to change to do work, nothing else is syncing to that machine right now. The other plugin doesn't exhibit this behavior as we have 5 jobs setup in the same manor, watching different labels, to run a job.