JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 65257
  • Score
    100M100P100Q205398F
  • License MIT

Return CI job number to run huge tests only on first job

Package Exports

  • ci-job-number

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ci-job-number) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

CI Job Number

Return CI job number to run huge tests only on first job.

Often we test different Node.js versions on Travis CI. But Node.js version doesn’t affect on many tests. For example, using external API for docs spelling check.

Since Travis CI is a free common resource, we should be responsible. So we can run big tasks only on first Node.js version.

const ciJobNumber = require('ci-job-number')

if (ciJobNumber() === 1) {
  runSpellingCheck()
} else {
  console.warn('To speed up CI spelling check runs only in first job')
}
Sponsored by Evil Martians

CI Support

  • AppVeyor
  • CircleCI
  • GitLab CI
  • Semaphore
  • Travis CI

Who Use It

Override Default Behaviour

CI_JOB_NUMBER environment variable will override CI job number. It is the best way to change default behaviour and run task on all CI jobs:

  - name: Build and test
    run: yarn test
    env:
      CI_JOB_NUMBER: 1