[JIRA] [git] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits
Eric Tucker commented on JENKINS-23606 Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits Any updates? Noticed this bug myself as well. 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.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Eric Tucker commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Can we please get this into the next release? Cannot upgrade Jenkins until this issue is resolved. 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.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Eric Tucker edited a comment on JENKINS-22750 Polling no longer triggers builds (regression 1.560) Can we please get this into the next release? Cannot upgrade Jenkins until this issue is resolved. The regression only broke polling for users with no slaves and using an SCM that requires a workspace for polling. So, most setups? The average installation of Jenkins is probably not using slaves and most are probably using git. This statement is ridiculous. 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.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Eric Tucker commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) If that's the recommended approach then the default installation of Jenkins should be configured with a master and a single slave by default. 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.
[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)
Eric Tucker commented on JENKINS-22750 Polling no longer triggers builds (regression 1.560) I mean that without any steps other than 'yum install jenkins' I should get the behaviour that is best practice. The average user is not going to know about slaves. I myself only found out about slaves because of this bug. If we're saying I should have been using slaves all along (and we've been using Jenkins for over a year) then there's a problem with the default setup. 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.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Eric Tucker commented on JENKINS-21394 Avoid queuing request for workspace while node is offline I don't think that's the issue Marek. I have projects with branches specified (some with hard coded values and some with wildcards) but none without a branch specified. 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.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Eric Tucker commented on JENKINS-21394 Avoid queuing request for workspace while node is offline Git Client 1.8.0 Git 2.2.1 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.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Eric Tucker commented on JENKINS-21394 Avoid queuing request for workspace while node is offline Since this issue is pretty widespread and seems to affect polling in general, can we please revert for the next release until the cause is identified? 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.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Eric Tucker commented on JENKINS-21394 Avoid queuing request for workspace while node is offline Is it possible this change broke something with polling? I updated to the latest version of Jenkins today and now all of my polling jobs keep displaying errors like this: Started on Apr 22, 2014 10:33:58 AM We need to schedule a new build to get a workspace, but deferring 8,741ms in the hope that one will become available soon (all_suitable_nodes_are_offline) Done. Took 0 ms No changes These jobs and polling all worked prior to the update. 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.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Eric Tucker commented on JENKINS-21394 Avoid queuing request for workspace while node is offline I am not using slaves. I have never used slaves. I have one build server with Jenkins running as (I assume) the master. It's been up all morning (hours) and the issue keeps happening on every polling attempt. 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.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Eric Tucker edited a comment on JENKINS-21394 Avoid queuing request for workspace while node is offline I am not using slaves. I have never used slaves. I have one build server with Jenkins running as (I assume) the master. It's been up all morning (hours) and the issue keeps happening on every polling attempt. Edit: reverting to Jenkins 1.559-1.1 through yum seems to address the issue as my builds immediately started polling successfully after reverting. 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.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Eric Tucker commented on JENKINS-21394 Avoid queuing request for workspace while node is offline I am polling git at intervals between 2 and 5 minutes. I cannot afford to move to the latest version at this time to facilitate logging. If there's any further information I can provide without going to the latest version I would be happy to provide it. 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.
