hobbs / jirret Goto Github PK

Consider having two jira projects with ids like "ABC" and "BC". Then you create a commit with a subject line saying "ABC-1 bugfix for blah blah".

As a result two jira issues will be commented by jirret: ABC-1 and BC-1.

re.findall is too greedy.

issue_needle = '(%s-[0-9]+)'
matches = re.findall(issue_needle % p, issue_haystack)

I've been told that when the hooks are called the working path is the git repo. So the script should just run normal git commands instead of using 'gerrit query' via the gerrit sshd.

This would make the setup of this hook simpler.

What license are you placing this code under?

So for example, in this commit message:

SAT-666 fix bug that prevents hailing

The ticket ID, as displayed in Gerrit, would be replaced with a link to that ticket on JIRA. I don't know if Gerrit can be configured to do this (just for display… of course we wouldn't want the actual commit message to be changed), or if it's out of the scope of this project.

It's a pain to have to ssh in and run "./jirret-process-hook update-projects", the script should probably auto update the projects periodically, or maybe it should just not store a list of projects on the FS, and just store them in memory.

Currently jirret seems to be running fine only when python 2.7 is installed.
Unfortunately standard installation for most production servers is python 2.4 :(

Jira has deprecated the xmlrpc interface in favour of their REST API, starting with Jira-7 release. Since jirret only uses the xmlrpc interface, this would presumably mean that jirret needs to be altered to use the newer API.