Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect CI Environment variables when collecting metrics #140

Open
robinjhuang opened this issue Jul 25, 2024 · 0 comments
Open

Detect CI Environment variables when collecting metrics #140

robinjhuang opened this issue Jul 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@robinjhuang
Copy link
Member

Would be nice to detect CI environments and include that as a flag in metrics that are collected to avoid counting CI environments in the target metric.

CI:
Many CI systems set this to "true" or "1"
CI_NAME:
Identifies the specific CI system (e.g., "travis-ci", "circleci")
TRAVIS:
Set to "true" in Travis CI environments
CIRCLECI:
Set to "true" in CircleCI environments
JENKINS_URL:
Present in Jenkins environments
GITLAB_CI:
Set in GitLab CI environments
GITHUB_ACTIONS:
Set to "true" in GitHub Actions environments
BITBUCKET_COMMIT:
Present in Bitbucket Pipelines
TEAMCITY_VERSION:
Present in TeamCity environments
APPVEYOR:
Set to "True" in AppVeyor environments
DRONE:
Set to "true" in Drone CI environments
BUILD_NUMBER or BUILD_ID:
Often set in various CI systems
@robinjhuang robinjhuang added the enhancement New feature or request label Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant