|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I have a similar issue with jobs that are configured for git push notification.
After upgrading from 1.557 to 1.563/1.564, these jobs no longer get triggered on repository checkins.
There is an entry in the system log indicating that Jenkins received the notification:
As git push notification involves configuring the job for scheduled polling, I believe I'm facing the same issue as reported here.
My setup:
The master (Debian 6) has 3 executors. There are 3 slaves configured (1 ssh unix slave and two jnlp Windows slaves) that are offline by default.
The jobs in question are not bound to any node or label.
Installed plugins: Parameterized Trigger plugin, Credentials Plugin, Hudson Fitnesse plugin, Matrix Project Plugin, SSH Slaves plugin, Mailer Plugin, Javadoc Plugin, OWASP Markup Formatter Plugin, Matrix Authorization Strategy Plugin, CVS Plug-in, Translation Assistance plugin, SCM API Plugin, cucumber-reports, LDAP Plugin, Maven Integration plugin, Green Balls, PAM Authentication plugin, Artifactory Plugin, GIT plugin, Ant Plugin, Windows Slaves Plugin, External Monitor Job Type Plugin, Copy Artifact Plugin, Extra Columns Plugin, MapDB API Plugin, SSH Credentials Plugin, promoted builds plugin, Multiple SCMs plugin, Subversion Plug-in.
GIT plugin is 1.1.26, all other plugins have the most recent version.