-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate docker and npm publish part #496
Conversation
Codecov Report
@@ Coverage Diff @@
## master #496 +/- ##
=====================================
Coverage 92% 92%
=====================================
Files 219 219
Lines 9280 9280
=====================================
Hits 8538 8538
Misses 742 742 Continue to review full report at Codecov.
|
531288f
to
84671a4
Compare
@@ -20,9 +20,36 @@ jobs: | |||
- run: npm install | |||
- run: npm test | |||
|
|||
deploy: | |||
docker: | |||
- image: circleci/node:8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it really has to be circleci node ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really.
Technically it could be any docker image that has got npm
; however I decided to reuse the same because
- As it has been already downloaded and built, it should start almost immediately.
- The
deploy
job has a transitive dependency on node8 build — therefore it's kind of a natural dependency.
If you have another idea around that feel free to shout them!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got it, this is image for build process, not for release. good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…odeploy Automate docker and npm publish part
This PR should hopefully allevieate the amount of work we have to do when we want to
release a new express-gateway version.
It will listen on the master branch and if a new tag with vx.y.z pattern comes in, it will build and publish both npm package and docker images related, and update the 'latest' tag as well.
We need to set both docker and npm credentials through env variables (//cc @kevinswiber )
Unfortunately I can't test this properly without deploying something — so once merged we could give it a try on eg 1.4 or any bug fix that'll come along us.
Connects #495 closes #495