coverage publish
Upload coverage reports to the Qlty Cloud
The qlty coverage publish command uploads code coverage reports to Qlty Cloud for analysis. It supports multiple report formats to ensure compatibility with various programming languages, including simplecov, clover, cobertura, coverprofile, lcov, jacoco, and the generic qlty format.
Beyond uploading reports, this command allows the addition or removal of file path prefixes, tagging uploads for easier identification, and overriding the value of certain git-related variables. It integrates code coverage data into Qlty Cloud, offering a comprehensive view of your codebase’s coverage.
Arguments
[PATHS]...
One or more paths to the coverage reports to be uploaded
--dry-run
Do not upload the coverage report, only export it to the output directory
--format
--format
The format of the coverage report to transform. If not specified, the format will be inferred from the file extension or contents [possible values: simplecov, clover, cobertura, coverprofile, lcov, jacoco, qlty]
--tag
--tag
--override-build-id <OVERRIDE_BUILD_ID>
Override the build identifier from the CI environment
--override-branch <OVERRIDE_BRANCH>
Override the branch from the CI environment
--override-commit-sha <OVERRIDE_COMMIT_SHA>
Override the commit SHA from the CI environment
--override-pr-number <OVERRIDE_PR_NUMBER>
Override the pull request number from the CI environment
--add-prefix <ADD_PREFIX>
The prefix to add to file paths in coverage payloads, to make them match the project’s directory structure
--strip-prefix <STRIP_PREFIX>
The prefix to remove from absolute paths in coverage payloads to make them relative to the project root. This is usually the directory in which the tests were run. Defaults to the root of the git repository
-t, --token
-t, --token
The token to use for authentication when uploading the report. By default, it retrieves the token from the QLTY_COVERAGE_TOKEN environment variable
--project
--project
The name of the project to associate the coverage report with. Only needed when coverage token represents a workspace and if it cannot be inferred from the git origin
--print
--verbose
-q, --quiet
--total-parts-count <TOTAL_PARTS_COUNT>
The total number of parts that qlty cloud should expect. Each call to qlty publish will upload one part. (The total parts count is per coverage tag e.g. if you have 2 tags each with 3 parts, you should set this to 3)
Example
Upload a Cobertura report to Qlty Cloud: