search

coverallsapp / orb

Coveralls CircleCI Orb
https://circleci.com/orbs/registry/orb/coveralls/coveralls
MIT License
2 stars 16 forks source link

Different build number when re-running failed steps #13

Closed MartynasSapoka closed 1 year ago

MartynasSapoka commented 3 years ago

I have a CircleCI setup with parallel build steps. Each step runs a part of the test suite and generates a coverage report.

Sometimes one of the steps fails unexpectedly and I just re-run them. But CircleCI assigns a different CIRCLE_WORKFLOW_ID on each re-run step, which means coverage gets uploaded to a new build on Coveralls.

Any suggestions how to overcome this? I would expect the coverage to be uploaded to the same build number when just re-running a failed build.

mrexox commented 1 year ago

There is an option carryforward which is used to provide a comma-separated job flags used in parallel jobs. You can check this example for usage. In that case the failed jobs will be carry-forwarded from previous builds.

Make sure you've upgraded the orb version to @1.0.7 or even better to @2.0.0.

A small note: after triggering parallel_finished: true results can no longer be uploaded to the build. So, it's better to rerun the whole suit.