- portability (change build servers, migrate to new instances etc)
- consistency (devs can run identical builds)
- versioned (in the repo)
- utilities (add other tasks to do things e.g. check package versions used, bump version numbers etc)
- branch builds/verison numbering between deploys
- could use the script, but have two TeamCity builds
- start using package restore?
- means you need access to the internal feed...
- but your repo size should be smaller
- gulp
- huge community
- fairly easy to grok
- per machine setup: install npm,
npm install -g gulp - per project setup:
npm install - run a build:
gulp - run a specific task:
gulp test:acceptance
- cake
- its c#
- it shares a name with a javascript build tool, good luck on google
- syntax seems more verbose than I like, but thats just my pref
- thats all I know about it
- fake
- its f#
- it's been around for years
- I heard if you want to start learning F#, this is a reasonable way to get your feed wet
- thats all I know about it
- make
- I know nothing about this
- I've heard good and bad things
- shell script
- primitive
- tasks etc are harder to write/chain
- might as well use make?