After the latest upgrade to Version 0.10.12-SNAPSHOT-2.0.0, I can't setup subversion repositories. I had 1 setup before the upgrade which was dropped by the new version but I can't import it back nor add it back again.
The Add-On presents me with 2 options:
1. Import repositories from the Atlassian's JIRA Subversion plugin configuration which fails with an error:
Import repositories result
2. Add which fails with either:
JIRA doesn't have a "Stop" option. I can disable it. I don't know where the "Index Directory" is.
Please help. I would like to clean start and set up my subvesrion directory from start.
Ok, I got 2.1.6 to work. I disabled the plugin, deleted the repository and truncated AO_C07F3E_SWCPROPS table. Then, re-enabled the plug-in. I had added a repository before I upgraded to the 2.1... versions, so I added the same repository but named it differently, shorten all 3 Content Management sections to be under 250 chars, than it worked. Then I went back and re-named the repository to its original name.
Wow, that was fun...
The right button name is "Disable" not "Stop", sorry for the confusion.
The repository index file is located at:
in the 2.0.0 version.
You might also see the old index path: pbeltranl-subversion-revision_h2 (or any similar name).
Disable the plug-in, delete all the index files and Enable it again.
The error that you reported:
Cannot insert duplicate key...
(which needs to be more user friendly) means that you are trying to register a repository with the same name or root url. The repository configuration is stored by using ActiveObjects, so even if you delete the index file, they will reamain registered. Anyway, they shuold work.
If after upgrade the plug-in, it looks like it is indexing nothig, it's because the Indexer process lost its value (default is 60 minutes). You have to set back it again (for example 1 minute) and wait to be fired by JIRA. You can schedule the indexer from the Administration > Advanced > Services menu:
and if you want to register the repositories again, please do it from the plug-in addministration page. You can see at the bottom the current registered, edit and delete them. Adding new ones and importing any previously repository registered with the Atlassian's plug-in:
Hope this helps.
Thank you Pablo for your quick response. I disabled the plugin, deleted all 4 index directories, deleted all entries in the sql table (so I wouldn't get dup messages), but I still see the Import option and it still fails to import or create a new repository (by new, I mean the same one I had before the upgrade). I tried uninstalling and re-installing but the same problem persists. I ended up reverting back to the previous version which worked.
I ended up reverting back to the previous version which worked.
The 1.x stores the configuration in JIRA properties (like the Atlassian's plug-in), while the 2.x in ActiveObjects.
There were some few bugs in the importing process (JIRA properties -> ActiveObjects) and they have already been fixed in the 2.1.0 version.
I have exactly the same problem. Had one working repository that disappeared with the latest plugin version and I'm not able to add a new repository.
In the table AO_C07F3E_SWCPROPS a new entry is added, but contains display_name, id and root_url only, everything else is 0 or null in that table, even if a provide a username and password for http basic auth.
I've already stoped the plugin, removed the index directory, cleared the database table and even reinstalled the plugin several times. Without success.
I'm using JIRA 5.2.8 with a mysql database if that helps.
By the way, where can I find the source code for this plugin? I think https://bitbucket.org/pbeltranl/jira-subversion-plugin-db doesn't contain the latest changes.
The display_name and the root_url attributes implement the unique constraint because no any other repository can be registered with the same name or url. That's OK. The bug seems in the part:
everything else is 0 or null in that table
The username and the password should be stored there if they were provided.
This looks related to some Active Objects bug in combination with MySQL and some JIRA version loosing the values for any no constrainted field. I've found a similar description of this behaviour reported by other user:
The problem reported by @Pavel at the beginning of the post is different: he is using MS SQL Server and the problem was due he was duplicating the name or the root url of an already registered repository. This error message has been replaced by one much more friendly. But getting some error message for that was right becuase the unique constraints.
Not too much clear for me, the 2nd issue reported by @Pavel:
I don't know whether it means that he tried to import the old configuration and failed (this bug has also been fixed) or whether it is the same bug reported by you (a wrong null configuration saved in the active object tables).
@Pavel: could you try the latest version (2.1.2) of the plugin and confirm whether all the bugs have been fixed and works fine for you?
Notice that if the 2.x version does not work, un-installing it and installing the 1.x version again should work wihout any other clean up task required as the 1.x and the 2.x version keep the configuration and the indexed data in different locations, without conflict.
I'm experiencing exactly the same problem - using Oracle 11 for database.
Tried fixing it by:
- disabling plugin
- removing the index files
- removing all lines in U_AO_C07F3E_SWCPROPS table
- re-enabling plugin
- initialiazing the active objects (as suggested)
- adding a new repository with only Display root, repo root and user + pw set. rest left to default values.
Reported error is still the same without any additional hint in red background field:
Hi @Sebastian and everybody,
could you try the just released 2.1.3 version?
It does not fix the problem but if the repository cannot be registered the configuration will be removed from the active objects avoiding to make a posterior clean-up and, more important, it will display the exception stack trace on the screen.
Thank you very much!
Ok. THANK YOU VERY MUCH.
The Web Client for Subversion allows users to indicate what types are text (so they can be compared) and what binaries.
Setting the Binary mime types field content (from the Add new repository form) to anything with a lenght < 255 characters, should work and allow you to try the plug-in.
Ah, thank you! Works now!
All the three fields mime types, encoding etc. were filled with too much data. After stripping some irrelevant types it worked.
Would be good to restrict the size of this field for the future :). However thanks a lot for helping out so quickly!
Accordig to some feedback received from other users, the 2.1.6 version looks like working fine on several database types.
So, my guess is that this time the problem could be in the Active Objects lazy initialization. Please, look at the plug-in administrator page: Is there some Error displayed in red saying that the Active Objects must be activated? If yes, please click on the link to resolve it, if not, let me know.
I just installed the latest 2.1.5 and am having the same problems as I reported initially (the first post that started all this). I can neither import my repository not add it back again. I get:
in both cases.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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