Write to VCS permissions are missing / No repo was created

Although this privilege was returned, apparently when "Manage git repositories for projects." is checked at http://git-dev.drupal.org/admin/settings/git-repo-manager, projects created *before* that was enabled do not get the privilege.

This situation shouldn't happen in production, but it will create tons of confusion in testing.

I don't think this is really a bug, if that setting is off there will be no repo, and if there's no repo for a given project, the checkbox doesn't show. Checking that setting won't go back and create a repo for al the projects that are missing repos.

Sorry I didn't realize this is against the build process.

The absence of the "Write to VCS" permission on the maintainers tab has so far indicated two separate and distinct problems on the backend, both of which resulted in the failure to create a repo.

The absence of a repo causes a number of other interface issues (you can't clone a non-existent repo, for example).

@sdboyer has made changes that should prevent the two known problems in the future, however he feels it's likely that additional beanstalkd issues will come up during testing. I'm wondering if it is unreasonable to wish for an error message when a repository doesn't exist?

Related issue #1031852: Create tests for existence of a repository after project creation

I'm updating this title since testers only see the absence of interface elements ("Write to VCS" permissions and missing "Git instructions" tab) and the failure of cloning (You can't clone an empty repo).

Developers are thinking of this as "There's no repository" and that has indeed been the cause of this issue so far.

This has been working reliably since fixes went in *and* we have tests for it, so I'm marking it fixed.