A guide to publishing a package to NPM using Travis.
This is a Work in Progress - modifying the pypi docs for NPM |
Step-by-step guide
Create a DevOps Support ticket to have DevOps get publish tokens for the edX NPMJS account and have DevOps add it to the travis config using the Travis CI command line client to encrypt the token:
Travis Admins/DEVOPS: Use the edx-semantic-release account and record the token in the Notes with the name of the package. NPM lets us have multiple tokens but doesn't let us label them.
travis encrypt --add deploy.api_key NPMTOKEN |
@edx
package scope (which you should!) you'll need to make sure you specify to npm that you still want the package to be public by doing this. npm version a.b.c
and it will update the version and tags for youIf your tag is in GitHub, but is not starting a build in Travis, or if you are deploying from too many sub-builds in Travis, see the following changes to .travis.yml.
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|