afinetooth
commented
2 years ago Hi, @dominikwilkowski.
While there's no way to create multiple coveralls projects for a single github repo (the relationship is 1-to-1), yours is a common case and this is the recommended approach:
You will probably want to configure coveralls.io to receive parallel builds for your project.
Specifically, what you'll do is modify your CI config file to build your project in parts, in parallel, often called a matrix build, where you'll send the node project coverage to coveralls.io in one parallel "job" and send the rust project coverage in another parallel job.
You're ahead of the game with a lcov.info file for your rust implementation. Nearly all coveralls integrations accept and process LCOV format coverage reports.
One integration that will be particularly useful / efficient for your use case is the Coveralls Github Action, which requires LCOV reports.
This usage example from the README demonstrates how to configure your Github Actions config YAML to send parallel jobs to coveralls.io.
In addition, the coveralls-node-demo project demonstrates the approach to configuring parallel builds for coveralls.io in the more general case, providing examples for Github Actions, CircleCI and Travis.
A so-called "matrix build" might not make sense for your project as they typically apply to running the same codebase against multiple different environments (like OS's).
Instead, you might just want to set up your project's CI builds with two (2) parallel jobs, in three (3) steps, like this:
Example using Coveralls Github Action
- Step 1: Run the tests for the node portion of your project. Convert the coverage report to
LCOVformat if necessary. Send the coverage report to coveralls with:
jobs:
tests:
steps:
name: Coveralls Node Parallel
uses: coverallsapp/github-action@master
with:
github-token: ${{ secrets.github_token }}
parallel: true
path-to-lcov: <path to `lcov.info` if not at `./coverage/lcov.info`>
flag-name: node-job- Step 2: Run the tests for the rust portion of your project. Convert the coverage report to
LCOVformat if necessary (sounds like it's not necessary). Send the coverage report to coveralls with:
jobs:
tests:
steps:
[...]
name: Coveralls Rust Parallel
uses: coverallsapp/github-action@master
with:
github-token: ${{ secrets.github_token }}
parallel: true
path-to-lcov: <path to `lcov.info` if not at `./coverage/lcov.info`>
flag-name: rust-job- Step 3: Close the parallel build by sending the parallel build (closed) webhook, like this:
finish:
needs: tests
steps:
- name: Coveralls Parallel Build Finished
uses: coverallsapp/github-action@v1.1.0
with:
github-token: ${{ secrets.github_token }}
parallel-finished: trueThe third step here is required. You must tell coveralls.io to close the parallel build before it will merge coverage reports from each job and calculate an aggregate coverage % for the full project.
Then you'll have both a single coverage report for the project as a whole, as well as individual coverage reports for each of the constituent jobs.
Hope that helps!
dominikwilkowski
I have a repo that includes a node and a rust implementation of the same thing. I have coveralls setup for the node implementation but now I don't know how to add the rust one. I have a
lcov.infofile for the rust coverage but since it comes from the same repo I fear it would just override the node one...Is there a way to create multiple coveralls project for the same repo basically?