| Name | JIRA Vault Plugin |
|---|---|
| Version | 1.0 |
| Product Versions | JIRA 3.6+ |
| Author(s) | Max Metral Brian Watson |
| Homepage | |
| Price | free! |
| License | |
| JavaDocs | |
| IssueTracking | http://confluence.atlassian.com/display/JIRAEXT/JIRA+Vault+Plugin |
| Download JAR | aalabs-jira-vault-plugin-1.0.jar aalabs-jira-vault.properties revisionindexservice.xml |
| Download Source | https://svn.atlassian.com/svn/public/contrib/jira/jira-vault-plugin/ |
Description/Features
This project is a port of the JIRA Subversion Plugin to work with the Vault source control provider. It creates another tab on each issue page that displays the Vault check-ins comments related to that JIRA issue.
Install Guide
- Shutdown JIRA
- Copy aalabs-jira-vault-plugin-1.0.jar to JIRA_INSTALL\atlassian-jira\WEB-INF\lib
- Edit the aalabs-jira-vault.properties file to have your settings.
- Copy your edited version of aalabs-jira-vault.properties to JIRA_INSTALL\atlassian-jira\WEB-INF\classes
- To enable log4j logging, add the following two lines to JIRA_INSTALL\atlassian-jira\WEB-INF\classes\log4j.properties
Logging
log4j.category.com.aalabs.jira = WARN, console, filelog log4j.additivity.com.aalabs.jira = false
You can change WARN to DEBUG to get more info.
- Copy revisionindexservice.xml to JIRA_INSTALL\atlassian-jira\WEB-INF\classes\services\plugins\vault
- In whatever directory you have configured JIRA to store its indexes, create the sub-directories plugins\atlassian-vault-revisions to be used by Lucene. For instance, if your indexes are configured to be in JIRA_INSTALL\indexes, then you need to create the directories JIRA_INSTALL\indexes\plugins\atlassian-vault-revisions
- Startup JIRA
- Confirm that the plugin is installed in JIRA by clicking Administration -> Plugins (under System) and viewing AALabs JIRA Vault Plugin.
- Confirm that the service is installed in JIRA by clicking Administration -> Services (under System) and viewing Vault Revision Indexing Service com.aalabs.jira.VaultRevisionIndexService.
- Read the atlassian-jira.log in JIRA_INSTALL\bin for any ERRORs or WARNings.
Usage
First, install the aalabs-jira-vault-plugin-1.0.jar as described above. Then when checking-in files in Vault, include the name of the related issue in the Vault check-in comments (ex: "BUG-10 comments..." where BUG-10 is the issue ID). Those comments will be indexed by the plugin and will appear in the Vault Commits tab on the identified JIRA issue.
Version History
Version 1.0 is our first, and so far our only, release.
Building From Source
The project was constructed using the Atlassian project template, so you can build the project using Maven .
C:\your\local\development\dir> maven jar
Open Issues
Screenshots
Screenshots |
|---|
|
|
Screen Shot
|
Comments (4)
Jun 22, 2006
Max Zelinski says:
Max, then you planning release this plugin? I'm very interested.Max, then you planning release this plugin? I'm very interested.
Oct 18, 2006
Daniel Vystrcil says:
Three items to report: 1) in the example properties file you have 'vault.reposi...Three items to report:
1) in the example properties file you have 'vault.repository', it should really be 'vault.repositories'
2) you also ask to create the 'atlassian-vault-revisions' folder under JIRA_INSTALL\indexes\plugins, this should not be done as lucene doesn't play well with the folder created by someone else.
3) could you add a property that will turn on or off the use of -ssl in the vault command line? I don't use that feature here and its throwing an error:
"The connection to the server failed: server cannot be contacted or uses a protocol tha..."
which can be seen completely when trying the same thing a true command line:
"System.Exception: The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. Unable to connect to . No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The underlying connection was closed: Could not establish secure channel for SSL/TLS."" rel="nofollow">https://my.vaultserver.com/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The underlying connection was closed: Could not establish secure channel for SSL/TLS."
I look forward to seeing this plug-in in action.
Thanks,
-- Dan
Feb 01, 2007
Rodney Brooks says:
When installing this plugin for the first time, why might I be getting the follo...When installing this plugin for the first time, why might I be getting the following logging errors (particularly the NoSuchMethodError). So far, I've tried v3.6.1 and v3.6.5 and the problem remains?
2007-02-01 19:04:00,929 DEBUG [com.aalabs.jira.VaultRevisionIndexService] getObjectConfiguration
2007-02-01 19:04:02,100 DEBUG [com.aalabs.jira.VaultRevisionIndexService] getObjectConfiguration
2007-02-01 19:04:11,991 DEBUG [com.aalabs.jira.VaultRevisionIndexService] getObjectConfiguration
2007-02-01 19:04:12,022 DEBUG [com.aalabs.jira.VaultRevisionIndexService] getObjectConfiguration
2007-02-01 19:04:34,053 DEBUG [com.aalabs.jira.VaultRevisionIndexService] running...
2007-02-01 19:04:34,053 DEBUG [com.aalabs.jira.VaultRevisionIndexService] getMultipleVaultRepositoryManager
2007-02-01 19:04:34,053 WARN [com.aalabs.jira.VaultRevisionIndexService] ComponentManager could not retrieve MultipleVaultRepositoryManager
2007-02-01 19:04:34,053 DEBUG [com.aalabs.jira.MultipleVaultRepositoryManagerImpl] constructor: ApplicationProperties
2007-02-01 19:04:34,053 DEBUG [com.aalabs.jira.VaultRevisionIndexer] constructor: MultipleVaultRepositoryManager, AppProps
2007-02-01 19:04:34,053 ERROR [com.aalabs.jira.MultipleVaultRepositoryManagerImpl] Failed to setup environment
java.lang.NullPointerException
at java.io.Reader.<init>(Reader.java:61)
at java.io.InputStreamReader.<init>(InputStreamReader.java:80)
at java.util.Properties.load(Properties.java:266)
at com.aalabs.jira.MultipleVaultRepositoryManagerImpl.setupEnvironment(MultipleVaultRepositoryManagerImpl.java:50)
at com.aalabs.jira.MultipleVaultRepositoryManagerImpl.<init>(MultipleVaultRepositoryManagerImpl.java:36)
at com.aalabs.jira.VaultRevisionIndexService.getMultipleVaultRepositoryManager(VaultRevisionIndexService.java:117)
at com.aalabs.jira.VaultRevisionIndexService.run(VaultRevisionIndexService.java:31)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
2007-02-01 19:04:34,084 DEBUG [com.aalabs.jira.MultipleVaultRepositoryManagerImpl] starting...
2007-02-01 19:04:34,084 DEBUG [com.aalabs.jira.VaultRevisionIndexer] starting VaultRevisionIndexer...
2007-02-01 19:04:34,084 DEBUG [com.aalabs.jira.VaultRevisionIndexer] RevisionIndexer.createIndexIfNeeded()
2007-02-01 19:04:34,084 DEBUG [com.aalabs.jira.VaultRevisionIndexer] IndexPath: D:\atlassian-jira-enterprise-3.6.5-standalone\indexes\plugins\atlassian-vault-revisions
2007-02-01 19:04:34,100 DEBUG [com.aalabs.jira.VaultRevisionIndexer] IndexPath: D:\atlassian-jira-enterprise-3.6.5-standalone\indexes\plugins\atlassian-vault-revisions
2007-02-01 19:04:34,100 WARN [atlassian.jira.util.LuceneUtils] Directory D:\atlassian-jira-enterprise-3.6.5-standalone\indexes\plugins\atlassian-vault-revisions does not exist - perhaps it was deleted? Creating..
2007-02-01 19:04:34,131 DEBUG [com.aalabs.jira.VaultRevisionIndexService] install
2007-02-01 19:04:34,147 DEBUG [com.aalabs.jira.VaultRevisionIndexService] getServiceManager
2007-02-01 19:04:34,147 ERROR [com.aalabs.jira.VaultRevisionIndexer] Error starting index service.
java.lang.NoSuchMethodError: com.atlassian.jira.service.ServiceManager.getServices()Ljava/util/Map;
at com.aalabs.jira.VaultRevisionIndexService.install(VaultRevisionIndexService.java:62)
at com.aalabs.jira.VaultRevisionIndexer.start(VaultRevisionIndexer.java:201)
at com.aalabs.jira.MultipleVaultRepositoryManagerImpl.start(MultipleVaultRepositoryManagerImpl.java:87)
at com.aalabs.jira.VaultRevisionIndexService.run(VaultRevisionIndexService.java:44)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
2007-02-01 19:04:34,163 DEBUG [com.aalabs.jira.VaultRevisionIndexer] IndexPath: D:\atlassian-jira-enterprise-3.6.5-standalone\indexes\plugins\atlassian-vault-revisions
2007-02-01 19:04:34,163 DEBUG [com.aalabs.jira.VaultRevisionIndexer] IndexPath: D:\atlassian-jira-enterprise-3.6.5-standalone\indexes\plugins\atlassian-vault-revisions
2007-02-01 19:04:34,194 ERROR [com.aalabs.jira.VaultRevisionIndexer] Indexing Error:
java.lang.NullPointerException
at com.aalabs.jira.VaultRevisionIndexer.updateIndex(VaultRevisionIndexer.java:98)
at com.aalabs.jira.VaultRevisionIndexService.run(VaultRevisionIndexService.java:46)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
Aug 03, 2007
kyle says:
I receive the following when the plugin is installed: 2007-08-03 17:05:27,047 J...I receive the following when the plugin is installed:
2007-08-03 17:05:27,047 JiraQuartzScheduler_Worker-2 DEBUG [com.aalabs.jira.VaultHistory] COMMAND STRING: /usr/bin/mono /usr/local/vault/vault.exe HISTORY -host myhost -user myusername -password [PASSWORD HIDDEN] -repository "Default Repository" $
2007-08-03 17:05:27,200 JiraQuartzScheduler_Worker-2 DEBUG [com.aalabs.jira.AbstractCli] RESULT: <vault><error>usage: HISTORY repository_path</error><result success="no" /></vault>
However, if that same command is run outside the plugin, I get the appropriate response. Any ideas what might be happening here?
Also, when the plugin is enabled, all the issue tabs (like comments) disappear - I'm running JIRA 3.10.
I appreciate any help, thanks.