Release Pipeline

[jpoon]

On a successful build of the release branch, Travis will:

1. Create a GitHub release uploading the packaged vsix
2. Publish the new version to the marketplace

Moving forward, for pushing a release, it will be:

1. merge master to release branch
2. git tag/gulp release and git push origin --tags

[rebornix]

Not quite sure but is it possible to put the key in Travis env instead of here?

[jpoon]

I think they would have the same effect. (https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings)

I would prefer putting it in this manner as then our configs are in one central location and not scattered about and my plaintext keys are not stored anywhere.

[johnfn]

This is really awesome! Can you please just add a little to a readme file somewhere documenting how to push a release? Since it's just going to be shared amongst the contributors, you don't have to go into that much detail. (I assume you just push to release and that's it?)

[jpoon]

@johnfn I simplified the release workflow removing the need to manage a release branch. Added instructions to the contributing.md.

In order to push a new release, all that is needed is to create a git tag. there's a helper function provided in the gulpfile for doing so: gulp patch|minor|major which will rev the package.json version as well as apply a git tag.

Travis will then:

1. build
2. test
3. publish the new version to the marketplace
4. create a GitHub release uploading the generated vsix

[johnfn]

LGTM. Thanks for maintaining our infra, @jpoon! It's a big help. :)