Support for coverage merging for multiple travis builds

[mfrister]

While #10 only concerned parallel_tests, I'd still be interested in merging the coverage results for multiple builds on Travis. Unlike parallel_tests, aggregation on filesystem-level is not possible with Travis as it isolates each build in seperate VMs or containers.

Until then, CodeClimate coverage reporting is useless for us (https://github.com/opf/openproject).

[calavera]

Thanks for starting this conversation @meeee.

I agree that we need to add support for aggregation on separated VMs/containers/hosts... I'm actively working on the backend for this purpose. But it needs to be handled carefully, I don't want to miss any one of your reports :) I cannot give you any ETA, because I really don't know when it's going to be ready, but I'll let you know as soon as it is.

[mfrister]

That's great to hear, thanks for the update!

[tessi]

@calavera thanks for tackling this problem!
Do you have any updates on the progress of this issue?

[JeanMertz]

👍 to this. Has there been any developments since August last year?

[brodock]

👍 we use codeclimate and circleci too and would like to have coverage aggregated. We saw that Coveralls recently release support for that.

[nj]

👍 too, as it can make quite a big difference when comparing before and after parallelism.

[grosser]

try this: https://github.com/grosser/cc-amend

[JeanMertz]

@grosser I don't see how that could work, given that the builds run in their own isolated environments, without access to their respective file systems.

[grosser]

Every build sends the partial coverage report to cc-amend and cc-amend joins them and forwards them to code-climate.

[pbrisbin]

I've created a new Issue to consolidate this with the 2 other similar issues. Please continue discussion there.