Web Links:

• FEDS - Directory Scanning Plugin - https://marketplace.atlassian.com/30318

Crucible Administrator's desire new Stash repositories to be automatically seen and added to Crucible (or to <insert atlassian product here>) on repo creation. One attempt to facilitate this using Crucible with the Directory Scanning Plugin (FEDS) installed had the following problem:
FEDS was configured to scan the Stash $STASH_HOME sub-directory data/repositories/ for new repositories. When repos are added to Stash the following things happen (among others)

1. a record is created in the database table 'repository'
2. a clone is created in the $STASH_HOME/data/repositories directory using the new db record's primary key as the directory name

FEDS added each repo it found in the directory to Crucible - but without any useful identifying information. Each repo was added using the directory name as the Crucible Repo name. And Crucible doesn't surface the repo description useful for identifying what repo ## really is.

My thought - if Stash provided a rest call to query repositories based on ID then the FEDS plugin could be modified to use the directory name in a rest call to pull Repository intel out of Stash - that way the Crucible Repo it then creates could have a meaningful name