Skip to content

Commit feb5100

Browse files
author
Steve Peak
authored
Merge pull request codecov#20 from briandant/master
Add further instructions for using env vars
2 parents 3f28e93 + 6802411 commit feb5100

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

README.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,14 @@ codecov
1313
codecov --token=<repo token>
1414
```
1515

16+
You can alternatively use the environment variables:
17+
18+
| Argument | Environment | Description |
19+
| -------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
20+
| `-t` | `CODECOV_TOKEN` | Private repo token for uploading |
21+
| `-e` | `CODECOV_ENV` | List of config vars to store for the build |
22+
| `-F` | | Flag this upload to group coverage reports. Ex. `unittests` or `integration` |
23+
1624
# How to generate coverage reports
1725

1826
[coverage.py](https://bitbucket.org/ned/coveragepy) is required to collect coverage metrics. Below are some examples on how to include coverage tracking during your tests. Codecov will call `coverage xml -i` automatically to generate the coverage xml output, which will be archived and processed server side.
@@ -75,7 +83,9 @@ This output is written by running the command `coverage xml` and states that the
7583

7684
**No**, these files contain coverage data but are not properly mapped back to the source code. We rely on `coveragepy` to handle this by calling `coverage xml` in the uploader.
7785

86+
####? How can I integrate with CICD providers?
7887

88+
Please see the documentation at our [Python repository](https://github.com/codecov/codecov-python/blob/master/README.md#ci-providers)
7989

8090
[1]: https://codecov.io/
8191
[2]: https://twitter.com/codecov

0 commit comments

Comments
 (0)