Nicholas 4f3c02d688 Ready to merge into master | hace 6 años | |
---|---|---|
.. | ||
CHANGELOG.md | hace 6 años | |
LICENSE | hace 6 años | |
README.md | hace 6 años | |
index.js | hace 6 años | |
package.json | hace 6 años |
Get details about the current Continuous Integration environment.
Please open an issue if your CI server isn't properly detected :)
npm install ci-info --save
var ci = require('ci-info')
if (ci.isCI) {
console.log('The name of the CI server is:', ci.name)
} else {
console.log('This program is not running on a CI server')
}
Officially supported CI servers:
ci.name
A string. Will contain the name of the CI server the code is running on.
If not CI server is detected, it will be null
.
Don't depend on the value of this string not to change for a specific
vendor. If you find your self writing ci.name === 'Travis CI'
, you
most likely want to use ci.TRAVIS
instead.
ci.isCI
A boolean. Will be true
if the code is running on a CI server.
Otherwise false
.
Some CI servers not listed here might still trigger the ci.isCI
boolean to be set to true
if they use certain vendor neutral
environment variables. In those cases ci.name
will be null
and no
vendor specific boolean will be set to true
.
ci.<VENDOR-CONSTANT>
The following vendor specific boolean constants are exposed. A constant
will be true
if the code is determined to run on the given CI server.
Otherwise false
.
ci.APPVEYOR
ci.BAMBOO
ci.BITBUCKET
ci.BUILDKITE
ci.CIRCLE
ci.CODEBUILD
ci.CODESHIP
ci.DRONE
ci.GITLAB
ci.GOCD
ci.HUDSON
ci.JENKINS
ci.MAGNUM
ci.SEMAPHORE
ci.TASKCLUSTER
ci.TEAMCITY
ci.TFS
(Team Foundation Server)ci.TRAVIS
MIT