nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Howto re-index SVN-repository with Subversion-Plus plugin for Jira?

HBT Infrastruktur Einzelaccount

We need possibility to change commit-messages in subversion and we want them to be updated in jira. Because of the incremental indexing of subversion-plus-plugin, usually they are not updated, I think a nightly re-indexing will do that.

how can we force subversion-plus to re-index the repositories. How ca we automate this?

Accepted answers

All comments

Contact Kintosoft

You do not need to re-indexing.

You can do it by using the web console (please see the animated gif attached in this issue SVN-59) which requires JIRA admin privileges or doing something similar by writting your own custom plugin using the public JAVA API to provide a GUI to allow others to make those modifications

HBT Infrastruktur Einzelaccount

Thanks for the answer. I would prefer to do that globally without knowing which jira-issue might be affected by a changed commit message. Developers here won't do what you showed in the animated gif even if we built a plugin, they will foget... 'That's why I thought of re-indexing...

Norman Abramovitz

There are directions in the documentation on how to re-index. It is not a clean process since sometimes communications between the plugin and svn breaks down and you need to restart indexing or restart Jira.

Contact Kintosoft

sometimes communications between the plugin and svn breaks down and you need to restart indexing or restart Jira

Do you mean there is not any way to continue indexing after some error accessing to a repository? This sounds like a bug as there are not too much reasons for that. It should continue as normal by:

clicking on the repository's Activate link
clicking on the indexing process' Start Now link
or simply waiting for the indexing process be fired by the scheduler

All the three above actions should continue indexing repositories after some network issue. If the indexing process stops indexing forever then there is a bug somewhere.

Contact Kintosoft

I would prefer to do that globally without knowing which jira-issue might be affected by a changed commit message

If I understood this well then it is not possible. Developers are the only persons knowing the issue that a commit is affecting to and this cannot be replaced by any automatic global process.

The plugin might help when a developer forgets or types a wrong issue key in the commit. In these cases it would be possible that the developer (or another person) fix the mistake without re-indexing the full repository from the beginning by following some of the instructions above.

There are add-ons on the Markeplace forcing developers to type a valid issue key in the commit message based on some rules. Maybe, they might be useful for you to avoid developers breaking traceability.

HBT Infrastruktur Einzelaccount

OK, I thought of something like deleting the index of subversion-add-on an rebuilding it from scratch, reading the subversion-commit-messages from the beginning every night. Perhaps that might become a performance issue but not having tried it, I would never know.

Therefor I do not have to know which commits or issues are affected by changed messages. In my eyes this might be possible but eventually not implemented.

HBT Infrastruktur Einzelaccount

I couldn't find those directions in the documentation, could you give a hint?

HBT Infrastruktur Einzelaccount

Seems, there is no possibility for reindexing a whole repository. The suggestion to do it inside the database ist no solution for us, so we haver to wait or to build a plugin by ourselves...:-(

Norman Abramovitz

Which version of subversion plus and Jira are you running since the directions changed as subversion plus developed into subversion alm. Also it would helpful which indexing structure you are using if you had a choice.

The general case was stop jira, delete a directory/database, start jira

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

moderators

addon-com.kintosoft.jira.subversion-plus