Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automatically deploy to npm upon merge to Master #3

Open
marcellodesales opened this issue Jul 18, 2015 · 2 comments
Open

Automatically deploy to npm upon merge to Master #3

marcellodesales opened this issue Jul 18, 2015 · 2 comments
Labels
enhancement hacktoberfest

Comments

@marcellodesales
Copy link
Member

Travis supports CD capability.

http://docs.travis-ci.com/user/deployment/npm/

Instead of forgetting to publish manually, this should be enabled. Here's our GitFlow workflow:

  1. Development occurs in the develop branch.
  2. New Pull Requests must be to to be merged against this branch. However, Pull Requests will only be reviewed If the pull request can be merged and the tests passes. Also, the milestone must be set to the associated Issue.
  3. After a new release has been planned, all the merged pull requests can be released.
  4. On a new release, Tagging is added, the version is bumped in package.json and the Develop branch will be merged to Master, triggering the npm publish on Travis.
marcellodesales added a commit that referenced this issue Jul 18, 2015
@marcellodesales
Issue #3: Adding CD from Travis to NPM
0100456 
This commit updates travis to properly make a new release upon a new
version of the applicaiton. Following the documentation at
http://docs.travis-ci.com/user/deployment/npm/, I did all the changes.

I first installed travis from Ruby Gems.

$ sudo gem install travis -v 1.8.0 --no-rdoc --no-ri -V

mdesales@ubuntu [07/18/2015 0:52:58] ~/dev/github/node-pom-parser
(master *) $ cat ~/.npmrc
//registry.npmjs.org/:_authToken=52****-****-***-***-*****cd9

mdesales@ubuntu [07/18/2015 0:53:19] ~/dev/github/node-pom-parser
(master *) $ travis encrypt --add deploy.api_key
Detected repository as marcellodesales/node-pom-parser, is this correct?
|yes| yes
Reading from stdin, press Ctrl+D when done
52****-****-***-***-*****cd9

From this, it completely updated the api value in the file
automatically. The only additional part added was about which branch it
should release from.

*	modified:   .travis.yml
- All the changes described above.
@marcellodesales marcellodesales self-assigned this Jul 18, 2015
@marcellodesales marcellodesales removed their assignment Aug 3, 2015
@dey-dey
Copy link

dey-dey commented Dec 14, 2015

+1

@foobar98
Copy link

@nsinghal12 I think this also needs some more access. Since I don't see an option to create a new workflow in the actions tab.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement hacktoberfest
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@marcellodesales @dey-dey @nsinghal12 @foobar98