Issue Type: Bug Bug
Assignee: Jesse Glick
Components: core, mercurial-plugin
Created: 18/Mar/15 9:20 AM
Description:

Our jobs are almost exclusively triggered by SCM changes. This way we avoid unnecessary builds of older releases or otherwise inactive branches. After upgrading from 1.602 to 1.604 on Monday, SCM triggered builds have stopped triggering.

This is not critical for nightly builds, as they are easy enough to set to periodical builds instead of SCM polling. However, for our continuous builds which poll regularly (more regularly than the actual build time), it's not really an option to set the builds to build periodically. Yes, the regularity could be lowered. But this could lead to a lot of failed build spam, if there are PMD issues or similar late one day.

After downgrading to 1.602, without downgrading plugins, builds started triggering again normally. I will retry with 1.605 in a few minutes, and see if this has been resolved in the latest release.

Environment: Jenkins 1.604
Updated plugins (based on JPI modification date - some do not show a previously installed version):
Ant Plugin 1.2
Environment Injector Plugin 1.91.1
External Monitor Job Type Plugin 1.4
HipChat Plugin 0.1.9
JUnit Plugin 1.5
Matrix Project Plugin 1.4.1
Multiple SCMs plugin 0.4
Script Security 1.13
SSH Credentials Plugin 1.10
SSH Slaves plugin 1.9
Static Analysis Collector 1.43
Static Analysis Utilities 1.71
Windows Slaves Plugin 1.0
Project: Jenkins
Labels: mercurial trigger scm
Priority: Major Major
Reporter: Sigmund Hansen
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.

Reply via email to