Detecting Other CI Services
Codecov automatically detects a wide variety of Supported CI providers. There are some exceptions, or new providers, that Codecov does not detect. In the event that your CI provider does not meet our matching criteria, you would need to provide the domain where your provider is located at.
This approach is particularly relevant if your CI meets any of the following critieria:
- It is hosted on-premises (e.g.,
- It is relatively new.
- It is a bespoke / custom CI that is not one of our mainstream supported CI providers.
Detecting an Unsupported CI Provider
Codecov detects CI services through the Commit Status API provided by GitHub/Bitbucket/GitLab. We review the target url, and context, in order to determine if the status is a "continuous integration service" that uploads coverage reports.
To manually add an unsupported CI, add the following to your codecov.yml:
codecov: ci: - jenkins.domain.com # add my custom jenkins server - somenewci.com # add a new CI Codecov does not support yet.
In addition to detecting CI's manually specified in the codecov.yaml, there is a match when
buildkite is found in the environmental variables context.
Ignoring a Specific CI provider
You can also ignore detecting the status of a specific CI provider. Below, we are ignoring AppVeyor. This is useful when, for example, you have not properly configured AppVeyor, or you are not expecting coverage reports uploaded from a CI provider.
codecov: ci: - jenkins.domain.com # add my custom jenkins server - !appveyor # ignore any statuses from appveyor
Updated 11 months ago