spec(deployment): the deployment system

[douglasduteil]

Deployment system

The component deployment is another independent key feature of the system. I was making a publishing system for angular-ui. In short it was making Travis CI the publisher of all releases based on source tagging. However it's already getting old and have various problems concerning the inner template customization and, recently, the sync of the pushed gh-pages on Github for a deploy key.

So for me the way to go is making more atomic module to play with. Here is my wishlist :

• [ ] Bumping system : deal with package.json, bower.json or *.json file with a version key.
• [ ] Git pusher : will push the code for you based on the package.json, bower.json or *.json file with a version key.
  • Can push tags.
  • Can push to a orphan branch
  • Can push only the content of a certain directory (like only the content of the dist directory)

--- inspred by angular-ui-publisher#publish.js

For me the best result is :

• [ ] No distribution files in the sources (master branch).
• [ ] A branch with it's own history (orphan branch) for the distribution files.
• [ ] Always double tagging on releases. Tag for the sources on the master branch (src1.2.3) for the release on the distribution branch (v1.2.3).
• [ ] The distribution branch must content :
  • [ ] The rooted distribution files
  • [ ] A package.json, bower.json or *.json file to expose the version etc...with no devdependencies.
  • [ ] generated CHANGELOG and README

--- inspired by ui-ace#bower

What you think guys @mgcrea @revolunet

[revolunet]

100% agree with having a separate dist branch with tags, usable with bower. Changelog + Readme also in the src of course

Does the bump automatically increment the minor version ? Can the user force the version number (say this is a major change) ?

[douglasduteil]

Does the bump automatically increment the minor version ? Can the user force the version number (say this is a major change) ?

Yes it's in the "Bumping system" for me I was thinking about using https://github.com/ikari-pl/gulp-tag-version maybe

[mgcrea]

@douglasduteil, something like vojtajina/grunt-bump (might worth checking: gulp-bump) would be nice indeed.

BTW, @revolunet tu me parlais de mercredi soir dans ton texto pour bosser sur ngFactory, on avait prévu quelque chose (demain du coup)?!

[douglasduteil]

Need to be forked not ?https://github.com/boennemann/grunt-semantic-release

[douglasduteil]

From :http://blog.hood.ie/2014/09/semantic-releases/

[mgcrea]

@douglasduteil nice pick, not sure about the fork, it may be faster to just restart from scratch, there is grunt stuff all over the place. Maybe we should create an issue about changing it to be build-tool agnostic and see if the author is interested.

[douglasduteil]

@mgcrea Agreed. I'm just starting getting how it's works....

[douglasduteil]

Pleasantly surprised

My dd-deploy is working with no modification for git commiting, tagging, and pushing.

I'm making a poke to connect is to Travis CI (for release publishing). And it works ! The setting up process is still to clarify and simplify. For now, the only requirement to make it work with TravisCI is by using :

• a deploy key : Can be generated by any collaborator and placed in the ~/.ssh folder. Pro : repo specific. Cons : A hell to setup ( see https://gist.github.com/douglasduteil/5525750#file-travis-secure-key-sh ).
• a github oauth token : Can be generated from any profile setting and placed in the repo remote URL as https://${GITHUB_TOKEN}@github.com/<user>/<repo>. Pro : less to de/encode. Just a Travis env to set. Cons : global access to all the repo.

[douglasduteil]

S'up boys

I gat my stuff working :) check the deployor I made : https://github.com/douglasduteil/node-git-deployor

[revolunet]

woot, looks cool :) poke = POC ?

the deploy key is the way to go. looks like we can replace the gem install with this : https://github.com/pwmckenna/node-travis-encrypt ?

[mgcrea]

Congratz @douglasduteil ! I'll check that this week!

On my side, I've worked on the gulp workflow this weekend and found some really interesting modules to refactor everything: lazypipe + gulp-inject, that enables to reuse any combination of transforms, and reinject this combination during the index.{jade,html} processing, it does really simplify the whole gulp file/process. I'll retrofit this into ngFactory very soon!

[douglasduteil]

:+1: