Comment 10 for bug 1012037

With the new deployment, the situation is a little bit better.

The problems we have right now are still with some git repository, that reach timeouts.
In particular:
- gcc git repository: cloned locally, it takes something like 96 minutes, way more than our max timeout; with this we might have another problem, since it is in a "detached HEAD" state, meaning that no default branch is set in the repository, and we might want to switch to "master" to perform "pull" operations on it (otherwise we will always get an error).
- other repositories take a lot locally too, might be good to increase the timeout again (now is 55 minutes, could be good to take it to 90) or ask IS to set up manually the repositories. This happens only on "clone" operations.

The other problem we could have is with "pull" operation when updating the already cloned repositories: as for the "gcc" one, not all of them have a default branch, nor a "master" one. We can deal with that in the code, but this means calling git, parsing output and making guess of what we might need, we do not have a way to specify a "branch" to be taken (worth adding it in the database?).