Subversion ALM - Repository Browser does not work

ARM Ltd. (old a

Hi

We are trying to evaluate the Subversion ALM PlugIn instead of Jira Subversion PlugIn.

There are some questions that we would like to clarify:

1. Is it necessary to Uninstall Jira Subversion Plugin when installing Subversion ALM one?
2. Does the Subversion ALM migrates data from Jira subversion Configuration or it is necessary to add all repositories again?
3. We are using WebSVN Subversion frontend which uses Apache Auth Basic Authentication via LDAP and seems the Subversion ALM Plugin integrated SVN Web Client does not support that kind of authentication and fails to login to repostory for browsing. At the same time seems Repository Reindexing is working properly.

Regards,

Areg

Contact Kintosoft

I have noticed that the plugin looses all the configuration when the Server ID is changed.

You can reuse databases by changing the SERVER ID. For example, you have an old instance binded to the SERVER_A and you want to reuse it from the SERVER_B. Then,

• Install Subversion ALM on the SERVER_B.
• Disable the plugin
• Replace the database file
• Enable the plugin
• Open the database web console
• Drop the current schema: DROP SCHEMA "CLIENT_SERVER_ID_B" (notice thah the server Id name uses underscore "_" rather than dashes "-" and is prefixed with "CLIENT_")
• Rename the old schema name by running: ALTER SCHEMA "SERVERID_A" RENAME TO "SERVER_ID_B"
• Re-start the add-on (disable + enable)

Could you please advise any way to backup the configured repositories so it will be possible to restore data after QA instance creation?

There are two approaches depending on what you need/want to.

In order to backup the full database, you can follow these H2 backup/restore instructions. To export few tables you might want to use CSV.

Also another question together with this - what is the best options to Backup/Restore configuration and the PlugIn data?

That depends on a lot of parameters. In most cases I would say this is not necessary because the add-on can be installed and configured easily and quickly. So you can be ready again within few minutes from the scratch.

For this cases, no-backups or ocasional backups by using the GUI provided by the web console would be enought (From the login Web console > Click on the "tools" link at the top of the page > Backup > fill out the required data -> This will create a backup on the JIRA server)

Unless you have many repositories (so it is hard to register them one by one), huge repositories (so indexing them could take some hours/days) or Subversion ALM is critical (so each second have to be taken in consideration) you might want to automate this process. In this case, you can write your own plugin, using the JIRA scheduling process and run a BACKUP command periodically). In order to restore it, I would say the the GUI provided by the web console is the best choice (tools > restore).

Keep in mind that the indexing process is quite robust as it is 100% ACID transactional (it relies on the H2 transactions). I mean if you lose 3 hours since the latest backup, there would not be much problems as the indexing process would detect the latest parsed commits and would go on from there without any problem (for all the registered repositories) in the meanwhile, the bundled Polarion web client for Subversion would work as normal because it access to Subversion directly. Only the calendars, the commit graphs and the JQL functions could be affected until all the repositories be fully indexed again.

Hope this helps.