Example Node GitLab CI Yamlfile

.gitlab-ci.yml

# Official framework image. Look for the different tagged releases at:
# https://hub.docker.com/r/library/node/tags/
image: node:6

before_script:
  - npm install

# This folder is cached between builds
# http://docs.gitlab.com/ce/ci/yaml/README.html#cache
cache:
  paths:
    - node_modules/

test:lint:
  script:
    - npm run lint

test:vulnerabilities:
  script:
    - npm run vuln-test

# Supported node versions can be found here:
# https://github.com/nodejs/LTS#lts_schedule
# jest does not support node < 4
# https://facebook.github.io/jest/docs/troubleshooting.html#compatibility-issues
test:node:6:
  script:
    - npm install -g codecov
    - npm run build
    - npm test && codecov

test:node:7:
  image: node:7
  script:
    - npm run build
    - npm test

test:node:4:
  image: node:4
  script:
    - npm run build
    - npm test

# Publish tagged versions to npm
publish:
  stage: deploy
  only:
    - tags
    - triggers
  script:
    - npm run build
    - echo '//registry.npmjs.org/:_authToken=${NPM_TOKEN}'>.npmrc
    - npm publish

Any reason we npm run build every time instead of piping artifacts?

the gitlab says that the configuration is not valid when I upload this file. It shows error the error " This GitLab CI configuration is invalid: (): did not find expected key while parsing a block mapping at line 3 column 1 Learn more". COuld you please help?

@thornbill can you share with us the package.json file. I'm interested in a scripts for lint and vuln-test

And what about npm version and git push --follow-tags?

This gist is related to https://www.exclamationlabs.com/blog/continuous-deployment-to-npm-using-gitlab-ci/

@Izhaki it might be that building in a different environment may not work / produce different results.
So, this is a good test to:

1. check if that environment supports building this code at all / without any errors
2. check if the code that this environments' build produces, works