You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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"
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.
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!