Hello, I recently upgraded a Jenkins CI server from 1.516 (or so) to 1.553. For some reason on this new Jenkins build my git SCM puller sees a 'new change' about every hour or so. This causes a job to be triggered for each of the projects throughout the hour.
There are no obvious messages in the logs as to why this is happening. For some reason it's just not aware that it has tested that build already. Has anyone seen this weird behavior and know of a workaround? Cheers! -Tim -- 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. For more options, visit https://groups.google.com/d/optout.
