I was just trying to figure out this exact issue. Larger projects with subrepos really amplify this issue as well.
It would actually be quite nice if the deploy key interface worked like the user interface letting me create groups and each group has keys in it etc. Alternately letting a group admin create deployment "users" that can be added to the regular user groups would also work fine.
Update: I believe this is already working . I just upgraded my plan from the free 5 person plan to 10 and now on my manage team page i see an option to set an SSH Key. I remove the one i set on all my individual repos , moved it to here and everything seems to work fine!
Strange that this ticket would stay open for 3 years ...
I had been using the team account credentials to read source into our build server (Jenkins) but wanted to change the password. Couldn't find any mention of it on the site so raised a ticket, to be told team accounts aren't allowed anymore and sent me to this ticket. Seems the only work around is to create a "team user" that can read the source, but that blows one of my development slots.
What's wrong with having a read only team login, for build servers?