f118062594
* Fix workflow * Trigger * [auto] Update compiled version * [auto] Commit modules * Push Windows changes * Fix * [auto] Update compiled version * Try removing cwd * [auto] Update compiled version * Try with path module * [auto] Update compiled version * Fix path * [auto] Update compiled version * Use raw path * [auto] Update compiled version * Other path * [auto] Update compiled version * Avoid @action/exec * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * test * [auto] Update compiled version * Try with shelljs * [auto] Update compiled version * Fix my stupidity * Copy scripts to local dir * [auto] Update compiled version * Still use path * [auto] Update compiled version * Delete entrypoint.sh * [auto] Update compiled version * Make file executable * [auto] Update compiled version * Try using bash * [auto] Update compiled version
is-ci
Returns true if the current environment is a Continuous Integration
server.
Please open an issue if your CI server isn't properly detected :)
Installation
npm install is-ci --save
Programmatic Usage
const isCI = require('is-ci')
if (isCI) {
console.log('The code is running on a CI server')
}
CLI Usage
For CLI usage you need to have the is-ci executable in your PATH.
There's a few ways to do that:
- Either install the module globally using
npm install is-ci -g - Or add the module as a dependency to your app in which case it can be used inside your package.json scripts as is
- Or provide the full path to the executable, e.g.
./node_modules/.bin/is-ci
is-ci && echo "This is a CI server"
Supported CI tools
Refer to ci-info docs for all supported CI's