StackGenVis: Alignment of Data, Algorithms, and Models for Stacking Ensemble Learning Using Performance Metrics
https://doi.org/10.1109/TVCG.2020.3030352
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
56 lines
2.0 KiB
56 lines
2.0 KiB
4 years ago
|
# @npmcli/ci-detect
|
||
|
|
||
|
Detect what kind of CI environment the program is in
|
||
|
|
||
|
[](https://travis-ci.com/npm/ci-detect)
|
||
|
[](https://coveralls.io/github/npm/ci-detect?branch=master)
|
||
|
|
||
|
## USAGE
|
||
|
|
||
|
```js
|
||
|
const ciDetect = require('@npmcli/ci-detect')
|
||
|
// false if not in CI
|
||
|
// otherwise, a string indicating the CI environment type
|
||
|
const inCI = ciDetect()
|
||
|
```
|
||
|
|
||
|
## CIs Detected
|
||
|
|
||
|
Returns one of the following strings, or `false` if none match, by looking
|
||
|
at the appropriate environment variables.
|
||
|
|
||
|
* `'gerrit'` Gerrit
|
||
|
* `'gitlab'` GitLab
|
||
|
* `'circleci'` Circle-CI
|
||
|
* `'semaphore'` Semaphore
|
||
|
* `'drone'` Drone
|
||
|
* `'github-actions'` GitHub Actions
|
||
|
* `'tddium'` TDDium
|
||
|
* `'jenkins'` Jenkins
|
||
|
* `'bamboo'` Bamboo
|
||
|
* `'gocd'` GoCD
|
||
|
* `'codeship'` CodeShip (or any that set `CI_NAME` environment variable)
|
||
|
* `'travis-ci'` Travis-CI - A few other CI systems set `TRAVIS=1` in the
|
||
|
environment, because devs use that to indicate "test mode", so this one
|
||
|
can get some false positives.
|
||
|
* `'aws-codebuild'` AWS CodeBuild
|
||
|
* `'builder'` Google Cloud Builder - This one is a bit weird. It doesn't
|
||
|
really set anything that can be reliably detected except
|
||
|
`BUILDER_OUTPUT`, so it can get false positives pretty easily.
|
||
|
* `'custom'` anything else that sets `CI` environment variable
|
||
|
|
||
|
## Caveats
|
||
|
|
||
|
Note that since any program can set or unset whatever environment variables
|
||
|
they want, this is not 100% reliable.
|
||
|
|
||
|
Also, note that if your program does different behavior in
|
||
|
CI/test/deployment than other places, then there's a good chance that
|
||
|
you're doing something wrong!
|
||
|
|
||
|
But, for little niceties like setting colors or other output parameters, or
|
||
|
logging and that sort of non-essential thing, this module provides a way to
|
||
|
tweak without checking a bunch of things in a bunch of places. Mostly,
|
||
|
it's a single place to keep a note of what CI system sets which environment
|
||
|
variable.
|