[JIRA] [naginator-plugin] (JENKINS-26954) add ability to put out special message if max retries is hit with no successful build
william schilp created JENKINS-26954 add ability to put out special message if max retries is hit with no successful build Issue Type: Improvement Assignee: Nicolas De Loof Components: naginator-plugin Created: 13/Feb/15 12:56 PM Description: it would be very helpful if naginator could put out a message, or set an environment variable, when the maximum number of retries has been hit without a successful build. at this point, i cannot tell when a job has been completely abandoned due to max retries being exhausted. we use git for version control and i have a sippy straw connection to the main servers at HQ, so the git update tends to fail due to dropped connections. i need to know when the max number of retries has failed so i can know when the build of the product was not attempted because it could not update the code base. Project: Jenkins Labels: enhancement Priority: Minor Reporter: william schilp 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-20630) Jenkins fails to start
william schilp commented on JENKINS-20630 Jenkins fails to start i'm having the same problem, java crashes shortly after loading jenkins. rolling back fixes the problem. any idea when a fix will be available. i updated some of my plugins that now will not run because they need the newer jenkins. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
william schilp commented on JENKINS-20630 Jenkins fails to start i strongly agree with Jonathan. in addition, the only reason i upgraded my installation of jenkins was due to a message on the jenkins control page that indicated a new version of jenkins was available. i thought (apparently incorrectly) that the jenkins control panel would only tell me that a new version was available if that version was a stable release. if that is not the case, then the message should say: New (possible unstable) version of Jenkins (x.x.x) is available for download. NOTE: use at your own risk. 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/groups/opt_out.
[JIRA] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
william schilp commented on JENKINS-12998 Allows variable subistution for Job Restrict where this project can be run label _expression_ any chance of this getting in? i really hate having to replicate jobs just so they run on the correct hardware. schleprock 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
