I'm not sure why you guys are asserting that JIRA has regular problems that would affect the web service API somehow. There was a recent problem with a few users not getting recognized in JIRA that I solved a few days ago. The only times that it has been down in the last few months is are the few times I've taken it down for a 5 minutes or so to test a fix for the problem above. At worst, you'd just have to wait a few minutes to try your commit in this case. Long gone are the days that JIRA was down for hours at a time, and they aren't going to come back. That said, this seems like a pretty strict commit hook, and I can't promise that there will never be issues with JIRA that might make such a commit hook fail on a good commit.
,Wil From: Christoph Dorn [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 05, 2008 11:17 AM To: Ralph Schindler Cc: Matthew Ratzloff; Zend Framework - General; [EMAIL PROTECTED] Subject: [zf-contributors] Re: [fw-general] Re: [zf-contributors] Zend Framework SVN Commit Proposal Might want to make the ticket expression /ZF\-\d+/ just to make maintenance of the hook easier. You'll also want to prevent commits to tickets that are closed. That would require a JIRA lookup, which means Jira would have to be running 100% of the time and without load. Not sure that requirement can be met at this time but we are getting there. You could implement a separate lookup table that gets updated every time a ticket status changes using the same interface the IRC bot uses. This would decouple the SVN hook from JIRA which is important as JIRA seems to have regular problems. I think the lookup table will stay mostly in sync if the notification interface is reliable, but that would have to be tested. Christoph
