You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jesse Yates (Created) (JIRA)" <ji...@apache.org> on 2012/02/08 19:47:00 UTC
[jira] [Created] (HBASE-5354) Source to standalone deployment
script
Source to standalone deployment script
--------------------------------------
Key: HBASE-5354
URL: https://issues.apache.org/jira/browse/HBASE-5354
Project: HBase
Issue Type: New Feature
Components: build, scripts
Affects Versions: 0.94.0
Reporter: Jesse Yates
Assignee: Jesse Yates
Priority: Minor
Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
Steps you need to go through:
1) Build the project
2) Copy it to the deployment directory
3) Shutdown the current cluster (if it is running)
4) Untar the tar
5) Update the configs to point to a local data cluster
6) Startup the new deployment
Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450377#comment-13450377 ]
stack commented on HBASE-5354:
------------------------------
It could go in I think since its self-documenting...
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450981#comment-13450981 ]
Jesse Yates commented on HBASE-5354:
------------------------------------
And apparently its totally hosed on Chris Trezzo's machine... looking into it.
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Reopened] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Yates reopened HBASE-5354:
--------------------------------
Reopening issue, since its apparently useful. Actually came up yesterday with testing one of the pom changes I made. Can you give it another spin @stack and commit if you like it?
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch, bash_HBASE-5354-v1.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450379#comment-13450379 ]
Jesse Yates commented on HBASE-5354:
------------------------------------
there were some things I added later that made it a bit nicer - give me a day or so.
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450370#comment-13450370 ]
stack commented on HBASE-5354:
------------------------------
This script looks alright Jesse. You think we should add it to dev-tools?
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Resolved] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Yates resolved HBASE-5354.
--------------------------------
Resolution: Won't Fix
No one really seems to need this, particularly with being able to run from the source. Dropping it.
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450371#comment-13450371 ]
Jesse Yates commented on HBASE-5354:
------------------------------------
It seemed slightly useful, at least in testing between the source and a real cluster. I've got a new version somewhere that's a bit better - lemme see if I can find it.
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450969#comment-13450969 ]
stack commented on HBASE-5354:
------------------------------
I did this:
{code}
h-24-30:trunk stack$ pwd
/Users/Stack/checkouts/trunk
h-24-30:trunk stack$ ./dev-support/deploy.sh
{code}
Maybe we should just leave the script here attached to the issue and if folks start looking for it, we'll point them here. If uptake, commit later?
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Updated] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Yates updated HBASE-5354:
-------------------------------
Attachment: bash_HBASE-5354.patch
Attaching patch that does as described. Apply the patch and then run it from the /hbase as ./dev-support/deploy.sh -h to see the usage info.
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Yates updated HBASE-5354:
-------------------------------
Attachment: bash_HBASE-5354-v0.patch
Try this one out. This version:
* removes the need to specify the version
** allows the release option to be dropped
* drops the security build
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Updated] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse Yates updated HBASE-5354:
-------------------------------
Attachment: bash_HBASE-5354-v1.patch
Updated version - works on my Mac (OSX) and Chris Trezzo's linux box.
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch, bash_HBASE-5354-v1.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "Elliott Clark (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451108#comment-13451108 ]
Elliott Clark commented on HBASE-5354:
--------------------------------------
Looks good.
Minor nit. There some odd indenting at the beginning of the script.
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch, bash_HBASE-5354-v1.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450966#comment-13450966 ]
Jesse Yates commented on HBASE-5354:
------------------------------------
how did you try it? I've found it works when running from /hbase, maybe this is a start directory issue (yeah, its a pretty simple script...)?
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "Jesse Yates (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450975#comment-13450975 ]
Jesse Yates commented on HBASE-5354:
------------------------------------
Weird that it didn't work...
Initially, this was a pretty small test case, though maybe it would make sense to add this check (running locally from the tarball) to the release checklist. If we add it, we should probably roll this script in to make it easier to deal with (also no real way to see usage if its just attached to the jira).
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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
[jira] [Commented] (HBASE-5354) Source to standalone deployment
script
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450959#comment-13450959 ]
stack commented on HBASE-5354:
------------------------------
I tried it:
{code}
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Could not find resource '/Users/Stack/checkouts/trunk/hbase-common/dev-support/findbugs-exclude.xml'.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find resource '/Users/Stack/checkouts/trunk/hbase-common/dev-support/findbugs-exclude.xml'.
{code}
> Source to standalone deployment script
> --------------------------------------
>
> Key: HBASE-5354
> URL: https://issues.apache.org/jira/browse/HBASE-5354
> Project: HBase
> Issue Type: New Feature
> Components: build, scripts
> Affects Versions: 0.94.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Priority: Minor
> Attachments: bash_HBASE-5354.patch, bash_HBASE-5354-v0.patch
>
>
> Automating the testing of source code in a 'real' instance can be a bit of a pain, even getting it into standalone mode.
> Steps you need to go through:
> 1) Build the project
> 2) Copy it to the deployment directory
> 3) Shutdown the current cluster (if it is running)
> 4) Untar the tar
> 5) Update the configs to point to a local data cluster
> 6) Startup the new deployment
> Yeah, its not super difficult, but it would be nice to just have a script to make it button push easy.
--
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