From 54faa67224cdf7c20813a397ff98f47c1bf0a2c4 Mon Sep 17 00:00:00 2001 From: Trevor Bedford Date: Wed, 5 Sep 2018 22:41:32 -0700 Subject: [PATCH] Publish release branch to npm via Travis All that NPM needs is a NPM_TOKEN that can be obtained via the website. This was set as an environment variable in Travis. With this in place, publishing is just "npm publish" --- .npmrc | 1 + .travis.yml | 18 +++++------------- 2 files changed, 6 insertions(+), 13 deletions(-) create mode 100644 .npmrc diff --git a/.npmrc b/.npmrc new file mode 100644 index 000000000..ae643592e --- /dev/null +++ b/.npmrc @@ -0,0 +1 @@ +//registry.npmjs.org/:_authToken=${NPM_TOKEN} diff --git a/.travis.yml b/.travis.yml index 2bf920e73..b210e2844 100644 --- a/.travis.yml +++ b/.travis.yml @@ -9,16 +9,8 @@ script: - npm run build after_success: - if [[ "$TRAVIS_PULL_REQUEST" == "false" && "$TRAVIS_BRANCH" == "release" ]]; then - npm run gzip-and-upload; npm run redeploy-site; npm run rebuild-docker-image; fi -deploy: - provider: npm - email: jhadfiel@fredhutch.org - api_key: - secure: q3E48VryY2/SnW0fjuAlVbl6xoib9U6RvbuXF1hiyyuAnFq/YA3lr9sFEfQFVs6GyBZ5baus/yqWi4MNJyR3d7F89Zz2eGSLN8HdBPKk0br1xmdB8apczghzZDvSNijGVvfTneTS1WhoM+0Ta35slZ0nIBqHTfyY4sHDzaib9X6ztIdp3niwOy1/XK0W8caX32QH0q3chsE+5aLG41brLRSqMkGOx/ScNdOCnvEKd1B7NmAshcA3+vy0Ev4S1l3MMLgsXEeYEeV9dDEbGzV7vB5VLPw6oSSwK/tNgdFPtx/ycScUqT2sxmlZB2F3DD0iG1b/DoeCYby8zA801JwDCjhtbCyZDWqHuDK/PScy4VELPCVDZSGxPpuRsH8ijdsunAw3K+s1uehITGl+cJ64f3+8iymdEIcNp1moRA6YoavSYb7iar3fi1gpT3MpdYGszcpVCo7diuHCcDo19uUeevDDdTq8xXBrkqySiA3k2H2QuWyk7bzNDj3Oc+H6JoCyKvI6Jmb35Rfe87qMYCfVMCQGLCSvhLvhG3qt/AwBY4uWvubjoAZok9op1Jj8hFBiQCKzDJ492mumwVdGQ32+9qHUQIh5CMMm4cODk489DCtQ/D6CAuVzIR5ZdPeJLxRT7JGr9Zi7sZRkM+XaLzjPu0VbRTZil+7WHpVkapBnsR8= - skip_cleanup: true - on: - branch: release -notifications: - email: - on_success: never - on_failure: always + npm run gzip-and-upload; + npm run redeploy-site; + npm run rebuild-docker-image; + npm publish; + fi