I did not succes to link to coveralls

[fletort]

I add the option to link to my coverall result. ("--link=coveralls").
The Added file to my test result "Coveralls.io" seems to link to an unexisting build number.
How this one is know by TestSPace ?
Maybe it is possible to indicate to the client the build id ? (i have it in my workflow)

[fletort]

Ok...i undestand on my side
It seems to be based on the hash of the commit. The one used by testspace seems good.
The problem is the hash used on coverall side... I generate my test resulst/coverage with an action that make some comparaison with base branch (multiple test)... Maybe they are some problem with this part of my process. I need to look how build id (hash) is send to coveralls... but the problem is more on that side than on your side :-)

[fletort]

From the coveralls documentation:
PULL REQUEST BUILDS
In Coveralls, pull request builds are coverage reports for a pull_request commit your CI service has built in your CI environment.

In contrast to push builds, pull request builds are more complicated because they are based on a temporary commit on an ephemeral branch of your repo called the merge branch, making these builds prospective builds, rather than actual, historical ones, like push builds.

[fletort]

The problem seems to be that i send only coverage information to coveralls from "pull_request"... if i do that also on push, i think that should be ok....
From there doc:
IDEAL CI CONFIGURATION
Build all push builds, on all branches, and send coverage reports for them to Coveralls.
Optional: Build all pull_request builds, on all pull request branches targeting your default branch, and send coverage reports for them to Coveralls.

[fletort]

Yes this was the problem.
I was only sending my coverage report to coveralls on Pull_request... so build id matching the commit was not avaialble on coveralls side. By adding this job also on push event, all is ok now. (as indicated by coveralls documentation......)