I have imported the jira.xml from one instance to another, where both the instances were using Jira subversion plugin without any issues, but after the import I am unable to start the target Jirainstance and after removing the subversion plugin jar file from lib folder only I could start Jira.
Some repositories were configured in the source subversion of Jira instance and these repositories are not able to acces in the network of new Jira instance.
But I need to start Jira with subversion plugin, is there any way to delete all the configured repositries in subversion from backend (DB). I cant do it from UI because when Jira is not starting if I install subversion plugin..
Thanks in adnvance.. :)
Don't know how to remove some of repositories, but you can find repository links(URLs) in database with this query
from propertyentry, PROPERTYSTRING
then change wrong URLs in property_string table. If you will change incorrect URLs to some of your SVN repositories, login will fail and jira will start anyway. After that you can fix situation from web interface.
If this is not working for you, you may using different jira or svn plugin version than I am...
I don't have syntax, but you should do following:
1. List all IDs from propertyentry where (entity_name='jira.plugins.subversion.repo')
2. delete rows from PROPERTYSTRING matching those IDs
3. delete rows from propertyentry where (entity_name='jira.plugins.subversion.repo');
The problem is not in the data itself, it is in the data combined with the Atlassian's add-on. So, you may
1. Remove the old configuration as suggested by @Andris
2. Remove the plugin from JIRA by deleting it from your <JIRA_HOME>/plugins/installed-plugins directory.
Once JIRA is up you may:
1. Install the latest version of the Atlassian¡s plugin and then you should see the old repositories and delete them from the plugin GUI. However, if I remember it well, the plugin reads the configuration and starts indexing repositories synchronously just after enabling, so your plugin might not be fully enabled for several minutes.
2. Install Subversion ALM instead as it ignores the Atlassian's plugin configuration. This should work without any problem.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs