How to configure FishEye to regularly scan and auto-add repos on a git server directory path?

Hi!  Our git server and Fisheye application are on two different servers.  We're adding new repositories to the git server.  How do I configure our FishEye server (or addon) to regularly scan for and then automatically add to FishEye any newly-found git server repos?

FYI the Directory Scanning Plugin appears to only work with directories local to the FishEye server.  It does not accept repo locations like "git://gitserver/path/to/repos/i/want/automatically/added"

4 answers

1 accepted

Accepted Answer
1 vote

Hi Philip,

You could write a simple script that would detect new repositories (on the git server side) and use the FishEye & Crucible REST API to add those repositories: https://docs.atlassian.com/fisheye-crucible/latest/wadl/fecru.html#rest-service-fecru:admin:repositories 

Also note there is a python library with FishEye & Crucible Admin Repository client: https://bitbucket.org/atlassian/fecru-rest-examples/src

 

Hope this helps.

mac

1 vote

Hi @Philip Schlesinger,

As the plugin name suggests, the Directory Scanning Plugin only accepts directories. Repository locations that start with "git://" must refer to specific repositories, they cannot refer to a location / directory where you have multiple repositories.

So, only directories that are local to the FishEye server can be configured in that plugin. It does not accept remote repositories. I have tried this myself in a local instance.

In this case, you will need to manually add the repositories in FishEye, one by one.

According to our Git documentation, these are the URLs / Paths accepted:

git://server_name[:port]/path_to_repository
http://server_name[:port]/path_to_repository
https://server_name[:port]/path_to_repository
ssh://server_name[:port]/path_to_repository
file://[hostname]/path_to_repository

As can be seen, you should not have any problems using repository locations following the pattern git://gitserver/username/reponame.git.

If this answer was helpful, please allow me to ask you to mark my answer as accepted in order to have it in the top of the thread, also helping other customers.

Thanks in advance!

Kind regards,
Felipe Kraemer

"git@gitserver:/path/to/repos/i/want/automatically/added" doesn't work either

Neither does this: "git@gitserver:path/to/repos/i/want/automatically/added"

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira Ops

Jira Ops Early Access Program Update #2: Let’s talk severity levels

Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...

44 views 1 1
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you