8000 Add LCOV coverage reporting as a replacement for COVERALLS reporting · Issue #1172 · utPLSQL/utPLSQL · GitHub
[go: up one dir, main page]

Skip to content
Add LCOV coverage reporting as a replacement for COVERALLS reporting #1172
Open
@jgebal

Description

@jgebal

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0