[JIRA] [core] (JENKINS-28137) Static Short URLs for Jobs
Michael Haderman created JENKINS-28137 Static Short URLs for Jobs Issue Type: New Feature Assignee: Unassigned Attachments: screenshot.png Components: core Created: 28/Apr/15 6:00 PM Description: It would be nice if Jenkins had a short URL option that could be used when linking to a job. We document some of our more complex jobs in Confluence and occasionally job names need to change, so it would be nice if there was a static short URL we could use instead. Confluence has this built in and it's pretty handy. Project: Jenkins Priority: Minor Reporter: Michael Haderman 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] [subversion] (JENKINS-21164) Audit Failures in Windows Event Log
Michael Haderman updated JENKINS-21164 Audit Failures in Windows Event Log Change By: Michael Haderman (27/Dec/13 8:34 PM) Description: We have our SVN repository hosted on a Windows Server 2008 box (recently migrated from 2003) and every minute we get 20+ Audit Failure logs from the account that our Jenkins CI server uses to connect to the repository. If we put Jenkins into Shutdown Mode we stop seeing the Audit Failures. However, the Jenkins CI server is able to get check for svn updates just fine and jobs are always triggered when there are new commits.The real issue we have is that when there are real login failures its pretty hard to debug the problem, when there are all the false failures from Jenkins.I've attached the Widnows Windows Event Log details.Our repo and the jenkins ci installation are on different servers. 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] [subversion] (JENKINS-21164) Audit Failures in Windows Event Log
Michael Haderman created JENKINS-21164 Audit Failures in Windows Event Log Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: EventLogError.txt Components: subversion Created: 27/Dec/13 7:45 PM Description: We have our SVN repository hosted on a Windows Server 2008 box (recently migrated from 2003) and every minute we get 20+ Audit Failure logs from the account that our Jenkins CI server uses to connect to the repository. However, the Jenkins CI server is able to get check for updates just fine and jobs are always triggered when there are new commits. The real issue we have is that when there are real login failures its pretty hard to debug the problem, when there are all the false failures from Jenkins. I've attached the Widnows Event Log details. Our repo and the jenkins ci installation are on different servers. Environment: Windows Server 2003/2008 Project: Jenkins Priority: Minor Reporter: Michael Haderman 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-13338) Add ability to have Still Failing only send an email once
Michael Haderman created JENKINS-13338: -- Summary: Add ability to have Still Failing only send an email once Key: JENKINS-13338 URL: https://issues.jenkins-ci.org/browse/JENKINS-13338 Project: Jenkins Issue Type: New Feature Components: email-ext Reporter: Michael Haderman Priority: Minor The scenario that this would resolve is: 1) Run jenkins job once (in my case a selenium test) 2) If it fails don't send an email. Use Naginator to re-run the job 3) If it fails again send an email using email-ext 4) If it fails again, don't send any more emails 5) Send an email once it is stable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13293) Add cron syntax to set Time Zone
Michael Haderman created JENKINS-13293: -- Summary: Add cron syntax to set Time Zone Key: JENKINS-13293 URL: https://issues.jenkins-ci.org/browse/JENKINS-13293 Project: Jenkins Issue Type: Improvement Components: buildresult-trigger Reporter: Michael Haderman It would be nice to have the ability to set what time zone scheduled builds should run in. Common crontab syntax is TZ=GMT 30 11 * * * -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
