Awesome

CodecovCLI

CodecovCLI is a new way for users to interact with Codecov directly from the user’s terminal or CI platform. Many Codecov features that require the user’s interference can be done via the codecovCLI. It saves commits, creates reports, uploads coverage and has many more features.

• CodecovCLI
• Installing
  • Using PIP
  • As a Binary
    • Integrity Checking the Binary
• How to Upload to Codecov
  • How to Get an Upload Token
• Usage
• Codecov-cli Commands
  • create-commit
  • create-report
  • do-upload
  • create-report-results
  • get-report-results
  • pr-base-picking
  • send-notifications
  • empty-upload
• How to Use Local Upload
• Work in Progress Features
  • Plugin System
  • Static Analysis
• Contributions
  • Requirements
  • Guidelines
  • Dependencies
• Releases

Installing

Using PIP

To use codecov-cli in your local machine, or your CI workflows, you need to install it:

pip install codecov-cli

The above command will download the latest version of Codecov-cli. If you wish to use a specific version, releases can be viewed here.

Note: If you're installing in a pyenv environment, you may need to call pyenv rehash before the CLI will work.

As a Binary

If you would like to use the CLI in an environment that does not have access to Python / PIP, you can install the CLI as a compiled binary. Linux and macOS releases can be found here, along with SHASUMs and signatures for each released version. Binary releases are also available via Github releases on this repository.

You can retrieve the Binary for Linux directly from your command line as follows:

curl -Os https://cli.codecov.io/latest/linux/codecov
sudo chmod +x codecov
./codecov --help

Integrity Checking the Binary

The binary can be integrity checked using a SHASUM256 and SHASUM256.sig file. The process for macos and Linux is identical. Linux is as follows:

curl https://keybase.io/codecovsecurity/pgp_keys.asc | gpg --no-default-keyring --keyring trustedkeys.gpg --import # One-time step
curl -Os https://cli.codecov.io/latest/linux/codecov
curl -Os https://cli.codecov.io/latest/linux/codecov.SHA256SUM
curl -Os https://cli.codecov.io/latest/linux/codecov.SHA256SUM.sig

gpgv codecov.SHA256SUM.sig codecov.SHA256SUM

shasum -a 256 -c codecov.SHA256SUM

For macos you will want to use the macos distributions of the binary (e.g., https://cli.codecov.io/latest/macos/codecov)

How to Upload to Codecov

If desired, the CLI can be used as a replacement for our NodeJS Binary Uploader. To use the CLI to upload from your CI workflow, you need to add these commands:

pip install codecov-cli
codecovcli create-commit
codecovcli create-report
codecovcli do-upload

OR

pip install codecov-cli
codecovcli upload-process

codecovcli upload-process is a wrapper for create-commit, create-report and do-upload.

You can customize the commands with the options aligned with each command.

Note that these commands will automatically search your environment for a $CODECOV_TOKEN environment variable and use it if found. If you do not have a repository upload token, or global upload token, stored as an environment variable, you will need to pass it into each command manually, like so: -t {$CODECOV_TOKEN}.

How to Get an Upload Token

The following tokens are suitable for uploading:

• The Repository Upload Token: Found on the settings page of your repository, also viewable on the /new page when setting up a repository on Codecov for the first time.
• The Global Upload Token: Found on your organization settings page (e.g., https://app.codecov.io/account/<scm>/<org>/org-upload-token).

Usage

If the installation is successful, running codecovcli --help will output the available commands along with the different general options that can be used with them.

Usage: codecovcli [OPTIONS] COMMAND [ARGS]...

Codecov-cli supports user input. These inputs, along with their descriptions and usage contexts, are listed in the table below:

Codecov-cli Commands

Note: Every command has its own different options that will be mentioned later in this doc. Codecov will try to load these options from your CI environment variables, if not, it will try to load them from git, if not found, you may need to add them manually.

create-commit

codecovcli create-commit [Options]

create-report

codecovcli create-report [OPTIONS]

do-upload

codecovcli do-upload [OPTIONS]

create-report-results

codecovcli create-report-results [OPTIONS]

get-report-results

codecovcli get-report-results [OPTIONS]

pr-base-picking

codecovcli pr-base-picking [OPTIONS]

send-notifications

codecovcli send-notifications [OPTIONS]

empty-upload

Used if the changes made don't need testing, but PRs require a passing codecov status to be merged. This command will scan the files in the commit and send passing status checks configured if all the changed files are ignored by codecov (including README and configuration files)

Usage: codecovcli empty-upload [OPTIONS]

How to Use Local Upload

The CLI also supports "dry run" local uploading. This is useful if you prefer to see Codecov status checks and coverage reporting locally, in your terminal, as opposed to opening a PR and waiting for your full CI to run. Local uploads do not interfere with regular uploads made from your CI for any given commit / Pull Request.

Local Upload is accomplished as follows:

pip install codecov-cli
codecovcli create-commit
codecovcli create-report --code <CODE>
codecovcli do-upload --report-code <CODE>
codecovcli create-report-results --code <CODE>
codecovcli get-report-results --code <CODE>

Codecov will calculate the coverage results, and return them in your terminal, telling you whether your PR will fail or pass the coverage check.

Note: In order for Local Upload to work, it must be used against a commit on the origin repository. Local Upload does not work for arbitrary diffs or uncommitted changes on your local machine.

Work in Progress Features

The following features are somewhat implemented in code, but are not yet meant for use. These features will be documented once they are fully implemented in the CLI.

Plugin System

To provide extensibility to some of its commands, the CLI makes use of a plugin system. For most cases, the default commands are sufficient. But in some cases, having some custom logic specific to your use case can be beneficial. Note that full documentation of the plugin system is pending, as the feature is still heavily a work in progress.

Static Analysis

The CLI can perform basic static analysis on Python code today. This static analysis is meant to power more future looking Codecov features and, as such, is not required or in active use today. As more functionality dependent on static analysis becomes available for use, we will document static analysis in detail here.

Contributions

This repository, like all of Codecov's repositories, strives to follow our general Contributing guidlines. If you're considering making a contribution to this repository, we encourage review of our Contributing guidelines first.

Requirements

Most of this package is a very conventional Python package. The main difference is the static the CLI's analysis module uses both git submodules and C code

Before installing, one should pull the submodules with:

git submodule update --init

Then, install dependencies with

pip install -r requirements.txt 
python setup.py develop

The C code shouldn't require any additional setup to get running, but depending on your environment, you may be prompted to install compilers and supporting tools. If errors are generated during installation, it is likely due to missing dependencies / tools required of the C code. In many cases, resulting error messages should be clear enough to determine what is missing and how to install it, but common errors will be collected here as they are encountered.

Guidelines

There are a few guidelines when developing in this system. Some notable folders:

1. commands - It's the folder that interacts with the caller. This is where the commands themselves should reside. These commands are not meant to do heavy lifting. They only do wiring, which is mostly parsing the input parameters.
2. services - It's where the heavy logic resides. It's mostly organized by which command needs them. Commands should generally be thin wrappers around these services.
3. helpers - This is meant for logic that is useful across different commands. For example, logging helpers, or the logic that searches folders.

Dependencies

If external dependencies need to be added, it's important to check whether those dependencies have wheels available on PyPI with the any or universal2 platform tags. If those dependencies don't have those wheels available, then they will need to built during the CI, so they will have to be added to the list of dependencies in the --no-binary flag when building the requirements for the macos release in build_assets.yml.

Releases

The standard way to making a new release is the following:

1. Open a PR that increases the version number in setup.py. As a rule of thumb, just add one to the micro/patch version (e.g., v0.1.6 -> v0.1.7).

2. Get the up-to-date master branch locally and run the tag.release command from the Makefile.

$ make tag.release version=v<VERSION_NUM>

The version tag must match the regex defined on the Makefile (tag_regex := ^v([0-9]{1,}\.){2}[0-9]{1,}([-_]\w+)?$).

Note:
Releases with test word in them are created as draft.
Releases with beta word in them are created as pre-release.