Hi, several of our teams are now deploying products to Android, and as you can imagine that means working with Android Git forests...and the repo command.

All good, except that using the repo command completely hides the source code checkout etc from Bamboo, which means you lose all the ALM like features, getting JIRA references from commit logs, being able to see what source deltas go into a build and the testing etc, etc. Not good.

In addition, in tools like Crucible, we can't add 300 git repos to a Crucible project...well we can but obviously this gives Crucible indigestion. Plus, even if we limit the forest to a few key git repos, linked to the Crucible project, Crucible is still not able to anchor patches properly.

This is ultimate a problem in JIRA as well. You can manually sustain 300 app links to the 300 git repos in an Android forest.

The atlassian tools as a whole, need a completely new feature for dealing with a group of source code repos or a "forest". So that we can point Bamboo, or Crucible or JIRA to an Android style forest of Git repos and expect the tools to do something reasonable.

I'm guessing other companies are running into this sort of thing as well, I see this as an important feature for Atlsasian to be part of the Android develpment environment.

You can find out more about the repo command here:

http://source.android.com/source/version-control.html