Met up with Josh from Travis-CI yesterday and learned that there is now support for repo level secrets. Furthermore I think there should be sufficient memory to generate code coverage and other metrics. If not then soon there will be an upgrade to the OSS VMs to bump the memory to 3-4GB which should then definitely be enough.

This means it should become possible to generate code coverage docs on travis-ci and then upload them to some server. Note that the secret isnt available for PR's as it would then be possible to output the secret in a PR test run. The secret obviously can only be decoded on a single repo (ie. symfony/symfony) and we could then write a little script that only does the generation for specific branches (2.0, 2.1, master ..).

I could help coordinate the implementation of this, but I probably dont have time to do the actual scripting.

@Pascal: do you have an interest to work on this?
@Fabien: it would be useful for either me or the person taking over the implementation to have admin permissions. Semi-related it seems like travis-ci depends on someone logging into travis-ci.org every now and then to get an up to date admin token.

regards,
Lukas Kahwe Smith
m...@pooteeweet.org

PS: If anyone has questions about travis-ci, including the pro version for private repos feel free to contact me.
PPS: I dont have any financial relationship to travis-ci, I just like their services and how they are helping the OSS community