Generic error uploading Coverage reports

Support
1

Description

Starting sometime on July 16, we started getting an error on any attempt to upload coverage reports to CodeCov:
https://codecov.io: Error: Error uploading to Codecov: Error: Not Found

Below is the output from our Jenkins console, which shows the commands we are running to upload, which were working prior to Friday. Worth noting, two days earlier on July 14, we switched from the bashuploader to the new uploader because the Bash Uploader had stopped working.

16:14:14 + curl -Os https://uploader.codecov.io/latest/linux/codecov
16:14:14 + chmod +x codecov
16:14:14 + ./codecov -Z -t ******** -F integrationTests -C 45c75991b193161eb568dee200fc00792994e03c
16:14:14
16:14:14 _____ _
16:14:14 / | | |
16:14:14 | | ___ __| | ___ ___ _____ __
16:14:14 | | / _ \ / ` |/ _ / / _ \ \ / /
16:14:14 | || () | (| | __/ (| () \ V /
16:14:14 ______/ _,|_|____/ _/
16:14:14
16:14:14 Codecov report uploader 0.1.0
16:14:14 => Project root located at: /home/jenkins/fs/workspace/ars-accelerator_release-21.3.0.0 16:14:14 Searching for coverage files…
16:14:22 => Found 1 possible coverage files: *
16:14:22* integration-tests/target/site/jacoco/jacoco.xml
16:14:22 Processing integration-tests/target/site/jacoco/jacoco.xml…
16:14:22 Detected Jenkins CI as the CI provider.
16:14:22 Pinging Codecov: https://codecov.io/upload/v4?package=uploader-0.1.0&token=*******&branch=release-21.3.0.0&build=10&build_url=https%3A%2F%2Fjenkins.v0.messagegearslabs.com%2Fjob%2Faccelerator-omnibranch%2Fjob%2Fmessagegears-accelerator%2Fjob%2Frelease-21.3.0.0%2F10%2F&commit=45c75991b193161eb568dee200fc00792994e03c&job=&pr=&service=jenkins&slug=&name=&tag=&flags=integrationTests&parent=
16:14:22 Error!: Error: Error uploading to https://codecov.io: Error: Error uploading to Codecov: Error: Not Found

Commit SHAs

007954bac84d07bc672dab17cd30f31a1a26e2b5

Repository

A link to the repository in question
https://bitbucket.org/messagegears/messagegears-accelerator/

CI/CD or Build URL

Jenkins 2.281

Uploader

https://uploader.codecov.io/latest/linux/codecov

Codecov Output

16:14:14
16:14:14 _____ _
16:14:14 / | | |
16:14:14 | | ___ __| | ___ ___ _____ __
16:14:14 | | / _ \ / ` |/ _ / / _ \ \ / /
16:14:14 | || () | (| | __/ (| () \ V /
16:14:14 ______/ _,|_|____/ _/
16:14:14
16:14:14 Codecov report uploader 0.1.0
16:14:14 => Project root located at: /home/jenkins/fs/workspace/ars-accelerator_release-21.3.0.0 16:14:14 Searching for coverage files…
16:14:22 => Found 1 possible coverage files: *
16:14:22* integration-tests/target/site/jacoco/jacoco.xml
16:14:22 Processing integration-tests/target/site/jacoco/jacoco.xml…
16:14:22 Detected Jenkins CI as the CI provider.
16:14:22 Pinging Codecov: https://codecov.io/upload/v4?package=uploader-0.1.0&token=*******&branch=release-21.3.0.0&build=10&build_url=https%3A%2F%2Fjenkins.v0.messagegearslabs.com%2Fjob%2Faccelerator-omnibranch%2Fjob%2Fmessagegears-accelerator%2Fjob%2Frelease-21.3.0.0%2F10%2F&commit=45c75991b193161eb568dee200fc00792994e03c&job=&pr=&service=jenkins&slug=&name=&tag=&flags=integrationTests&parent=
16:14:22 Error!: Error: Error uploading to https://codecov.io: Error: Error uploading to Codecov: Error: Not Found

Expected Results

Successful upload

Actual Results

Error provided

Additional Information

2

@mg-johncamerin I’ll push a fix for this today or tomorrow. Can you confirm that the env variable VCS_SLUG exists in the Jenkins environment?

3

Hi, I ran into the same issue with the v2 uploader. Here is a Gist with relevant configs and information. This is a Django app and I use coverage.py to generate coverage reports from the Django unit tests.

Downgrading to v1 seems to have fixed the issue.

4

VCS_SLUG does not exist

Added this to my Jenkins pipeline

echo "Validating VCS_SLUG:${env.VCS_SLUG}"

and it spit out

Validating VCS_SLUG:null

Also tried

sh 'echo $VCS_SLUG'

and got nothing

1 Like
5

@mg-johncamerin got it, thanks for confirming. I went down the wrong rabbit hole first.

6

@mg-johncamerin I made an update to the uploader, are you able to try v2 again?

7

Yes. It is working now. Thank you

1 Like