Description

jgebal

opened on Dec 10, 2021

Issue body actions

Existing COVERALLS reporting is no longer easy to publish to COVERALLS.
If users would be using GithubActions/AzurePipelines etc., the preferred format would be LCOV.

The preferred way to publish coverage reports to Coveralls is via Coveralls App and this one accepts LCOV format.

The problem was discovered while trying to switch from Travis to GithubActions.
In fact, even existing Travis integration was not trivial as it required additional scripting on CI side to make the output JSON report consumable by Coveralss by adding MD5 hash for each source file reported.

A discussion on Coveralls led me to conclusion that the best approach would be to implement a new LCOV coverage reporter.

Activity

1. jgebal

   added

   enhancement

   idea

   reporter

   on Dec 10, 2021
2. jgebal commented on Dec 10, 2021

   

   jgebal

   on Dec 10, 2021

   MemberAuthor

   More actions

   Description of LCOV format can be found here
   A good interpretation of it can be also found in this parser, particularly in this file
3. lwasylow commented on Dec 11, 2021

   

   lwasylow

   on Dec 11, 2021

   Member

   More actions

   Don't we already publish code coverage in sonar cloud? Just wonder if the lcov is a niche? I think most people using Jenkins or azure which consume cobertura. Just wonder how much uptake it will have and how many people actually using this format?
4. jgebal

   removed

   reporter

   on Feb 22, 2022
5. jgebal commented on May 9, 2026

   

   jgebal

   on May 9, 2026

   MemberAuthor

   More actions

   Consider dropping support for coveralls as it didn't become widely adopted (especially in PL/SQL)
6. jgebal

   removed

   idea

   on May 9, 2026
7. jgebal

   changed the title [-]Add LCOV coverage reporting as a replacement for COVERALLS reporting[/-] [+]Consider dropping support for coveralls[/+] on May 9, 2026
8. jgebal

   changed the title [-]Consider dropping support for coveralls[/-] [+]Drop support for coveralls[/+] on May 9, 2026
9. jgebal

   closed this as completedin #1363on Jun 8, 2026

Issue actions