Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No CI detected for Cirrus CI

See original GitHub issue

Hello there, I’ve configured codecov-node for a CI build on Cirrus CI and I experience the following issue:

  _____          _  
 / ____|        | |  
| |     ___   __| | ___  ___ _____   __  
| |    / _ \ / _` |/ _ \/ __/ _ \ \ / /  
| |___| (_) | (_| |  __/ (_| (_) \ V /  
 \_____\___/ \__,_|\___|\___\___/ \_/  
                                v3.5.0
==> Detecting CI Provider
    Cirrus CI Detected
==> Configuration: 
    Endpoint: https://codecov.io
{
  commit: 'b18b3599b994a3ada48148905f245ac6ee730eff',
  branch: 'cirrus-codecov',
  package: 'node-v3.5.0'
}
==> Building file structure
==> Generating gcov reports (skip via --disable=gcov)
    $ find /tmp/cirrus-ci-build -type f -name '*.gcno'  -exec gcov  {} +
==> Scanning for reports
    + /tmp/cirrus-ci-build/coverage/lcov.info
    + /tmp/cirrus-ci-build/coverage/clover.xml
==> Uploading reports
    HTTP 400
service must be ci-provider

As you can see Cirrus CI was detected properly but while uploading artifacts server returned 400.

Issue Analytics

State:
Created 4 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

trivikrcommented, Oct 23, 2019

Yup, I too believe it’s a server-side issue. My findings can be viewed in https://github.com/codecov/codecov-node/issues/152#issuecomment-545566856 We just need to wait for @eddiemoore to comment

0reactions

drazisilcommented, Nov 25, 2019

This support has been deployed.

Top Results From Across the Web

Upload error from cirrus-ci - Support - Codecov

This works fine locally, but when the CI server runs the command I get $ ./node_modules/codecov/bin/codecov ... Cirrus CI Detected ==> Configuration:

Writing Tasks - Cirrus CI

Naming script instructions helps gather more granular information about task execution. Cirrus CI will use it in future to auto-detect performance regressions.

Computing Services - Cirrus CI

Cirrus CI is a modern Continuous Integration system built for the era of cloud computing. Cirrus CI supports Linux, Windows, macOS and FreeBSD...

Programming Tasks in Starlark - Cirrus CI

There's no need to introduce a full-blown compile and deploy process for a few dozen lines of logic. Starlark scripts can be executed...

Blog - Cirrus CI

As Tart matured, we started using it for Cirrus CI's macOS VM instances to ... Got it working or found a clue? Cool....