Detalhes do pacote

@qawolf/ci-info

watson36.7kMIT2.1.0

Get details about the current Continuous Integration environment

ci, continuous, integration, test

readme (leia-me)

ci-info

Get details about the current Continuous Integration environment.

Please open an issue if your CI server isn't properly detected :)

npm Build status js-standard-style

Installation

npm install ci-info --save

Usage

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')
}

Supported CI tools

Officially supported CI servers:

Name Constant isPR
AWS CodeBuild ci.CODEBUILD 🚫
AppVeyor ci.APPVEYOR
Azure Pipelines ci.AZURE_PIPELINES
Bamboo by Atlassian ci.BAMBOO 🚫
Bitbucket Pipelines ci.BITBUCKET
Bitrise ci.BITRISE
Buddy ci.BUDDY
Buildkite ci.BUILDKITE
CircleCI ci.CIRCLE
Cirrus CI ci.CIRRUS
Codeship ci.CODESHIP 🚫
Drone ci.DRONE
dsari ci.DSARI 🚫
GitHub Actions ci.GITHUB_ACTIONS
GitLab CI ci.GITLAB 🚫
GoCD ci.GOCD 🚫
Hudson ci.HUDSON 🚫
Jenkins CI ci.JENKINS
Magnum CI ci.MAGNUM 🚫
Netlify CI ci.NETLIFY
Nevercode ci.NEVERCODE
Sail CI ci.SAIL
Semaphore ci.SEMAPHORE
Shippable ci.SHIPPABLE
Solano CI ci.SOLANO
Strider CD ci.STRIDER 🚫
TaskCluster ci.TASKCLUSTER 🚫
TeamCity by JetBrains ci.TEAMCITY 🚫
Travis CI ci.TRAVIS

API

ci.name

Returns a string containing name of the CI server the code is running on. If CI server is not detected, it returns 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

Returns 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.isPR

Returns a boolean if PR detection is supported for the current CI server. Will be true if a PR is being tested, otherwise false. If PR detection is not supported for the current CI server, the value will be null.

ci.<VENDOR-CONSTANT>

A vendor specific boolean constant is exposed for each support CI vendor. A constant will be true if the code is determined to run on the given CI server, otherwise false.

Examples of vendor constants are ci.TRAVIS or ci.APPVEYOR. For a complete list, see the support table above.

Deprecated vendor constants that will be removed in the next major release:

  • ci.TDDIUM (Solano CI) This have been renamed ci.SOLANO

License

MIT

changelog (log de mudanças)

Changelog

v2.0.0

Breaking changes:

  • Drop support for Node.js end-of-life versions: 0.10, 0.12, 4, 5, 7, and 9
  • Team Foundation Server will now be detected as Azure Pipelines. The constant ci.TFS no longer exists - use ci.AZURE_PIPELINES instead
  • Remove deprecated ci.TDDIUM constant - use ci.SOLANDO instead

New features:

  • feat: support Azure Pipelines (#23)
  • feat: support Netlify CI (#26)
  • feat: support Bitbucket pipelines PR detection (#27)

v1.6.0

  • feat: add Sail CI support
  • feat: add Buddy support
  • feat: add Bitrise support
  • feat: detect Jenkins PRs
  • feat: detect Drone PRs

v1.5.1

  • fix: use full path to vendors.json

v1.5.0

  • feat: add dsari detection (#15)
  • feat: add ci.isPR (#16)

v1.4.0

  • feat: add Cirrus CI detection (#13)
  • feat: add Shippable CI detection (#14)

v1.3.1

  • chore: reduce npm package size by not including .github folder content (#11)

v1.3.0

  • feat: add support for Strider CD
  • chore: deprecate vendor constant TDDIUM in favor of SOLANO
  • docs: add missing vendor constant to docs

v1.2.0

  • feat: detect solano-ci (#9)

v1.1.3

  • fix: fix spelling of Hunson in ci.name

v1.1.2

  • fix: no more false positive matches for Jenkins

v1.1.1

  • docs: sort lists of CI servers in README.md
  • docs: add missing AWS CodeBuild to the docs

v1.1.0

  • feat: add AWS CodeBuild to CI detection (#2)

v1.0.1

  • chore: reduce npm package size by using an .npmignore file (#3)

v1.0.0

  • Initial release