Creating a static version of a JIRA
May 24th, 2008 by HenI’m finally getting near the end of my every now and then hacking at a static version of a JIRA.
The basic story is that I want to turn off the computer that is running in my attic doing nothing but hosting a JIRA. The slicehost I pay for isn’t a great place to try and squeeze in the memory hungry JIRA/JVM combination, and as the project has mostly moved to Google Code it seemed like a good idea to get the JIRA gone too. Google Code doesn’t have any simple methods for uploading the data (basically you get to do HTTP and have no control over dates etc), so I decided to dump JIRA as XML, and XSLT a nice look to it. Maybe one day I can migrate it to Google Code or elsewhere, but I doubt it matters.
Pulling the XML down is easy - in fact I don’t even implement that. I assume you have used the IssueNavigator in JIRA to get a dump of all your issues as RSS. That’s right - probably will make a big JIRA explode. Ah well. I also pull down attachments for you. Just not the audit history.
Then I use XSLT (stunning architecture eh?) to put together a simple static site that shows users, issues, projects and versions (couldn’t be bothered with components though I should add them some day). The nice part here is that as I have the xml, I can restyle and make it better if I ever want to. It will support the project and issue URLs out of the box, while version and user urls will require a mod_rewrite rule, however no one goes directly to those links anyway.
Here’s the site:
I need to redo it from the latest xml dump, and then maybe it will be done and that light hum from above can go quiet.
If you want the code to do this (you’ll have to modify it yourself as it’s got little hacks in for osjava specific bits) it’s public domain and available at:
https://svn.atlassian.com/svn/public/contrib/jira/jira-outlet/trunk/mig4jira/static