I've added this add-on to Fisheye.
I've selected all projects in Stash to be synced into Fisheye, but I'm only seeing a limited number, has this add-on been tests with a large number of stash projects?
The second part is the main selling point of Stash as a repo manager is the ability to support access control at a project, repo and down to branch level.
The repo sync does not import the stash permissions into fisheye and there is no programmatic way to apply LDAP filters to a fisheye repository. Any plans to add permissions into repo sync?
regards
Mike Brosnan
Hi Mike,
As I'm not familiar with this add-on I'm not sure about its limitations, so I'd suggest contacting Richard Stephens directly at rstephens@atlassian.com as in the description of the add-on to check this. Talking about FishEye itself, the only known limitation for number of repositories is if you are using a Starter License, which is limited to 5 repositories.
I'd like to call to attention that, besides not being a supported add-on, it seems to be a quite old add-on developed before FishEye offered a feature that easily allows you to add Stash repositories to FishEye just by having the Application Link created between the applications. You can check further about this in https://confluence.atlassian.com/display/FISHEYE/Integrating+FishEye+with+Stash right under Easily add Stash repositories to FishEye. Since FishEye 3.4 and Stash 2.11.4 you can go to FishEye Administration > Repositories > Stash Repositories
tab and add each repository you want just by clicking in the Add button. As you have many repositories I understand though this brings the inconvenience of not being able to select and add many repositories and/or projects at once, so I'd like to present you with two feature requests that suggest some changes in this matter - you may want to follow them as well to track their progress and add any suggestions: https://jira.atlassian.com/browse/FE-4753 and https://jira.atlassian.com/browse/STASH-2589.
Regarding permissions, I'm afraid there will be no ideal solution for now to get permissions from Stash, as they are managed separately, and also differ in a few points. Please check at Tim Pettersen's comment in https://answers.atlassian.com/questions/315403 for a further explanation on this and also a suggestion made by him. As an outcome of that topic I also found https://jira.atlassian.com/browse/FE-5276 which you may also want to track.
Regarding the LDAP filters, I'm afraid I also won't have a proper solution for this at the moment. The only thing I could think about that may help you is that the LDAP filter for a repository is set in the config.xml
file under your FISHEYE_INST directory. Atlassian doesn't recommend editing the config.xml directory, so this could be done at your own risk, but just for informing, this is how it's set under the repository configuration (check the ldap tag):
<repository name="stash392one" description="Added by grefosco on Fri 31 Jul 2015, 10:28 AM" store-diff="true" enabled="true"><git location="ssh://git@localhost:7999/proj/stash392one.git" renames="none" path=""><ssh-auth key-name="stash392one"/></git> <linker/><security use-defaults="true" allow-anon="false" allow-logged-in="false"><required-groups/><ldap filter="uid=${USERNAME}" match-type="user"/></security> </repository>
As I presented you with a few feature requests, I'd like to also present you with the Atlassian policy for the implementation of new features for your reference.
Regards,
Gustavo Refosco
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.