driftyco/ionic — pull request #533 by ajoslin (2014-02-05 01:04:27+00:00)
Title: chore(build): more ci server automation

#523

**Changes**

- Remove and gitignore dist folder
- Add `release` folder, where release files are put every full release
- Added current version to release folder just to have something in there

**Additions**

- On every travis build, do the following:
1. Build / jshint
1. Check for mistakes (xdescribe, iit, xit, ddescribe, merge conflicts)
1. Unit test
1. For every commit that's not a release commit:
a. Make a 'build version' (eg `v0.9.23-alpha-3-a062c08`)
b. Push to bower-ionic repo with build version
c. Push to ionic-code/nightly with build version
1. If it's a release (triggered by running ./scripts/release/ files, see README#development):
a. Put built files in `release` folder on ionic main repo
b. Push to bower-ionic repo with release version
c. Push to ionic-code/{version}
d. Push to ionic-angular-cordova-seed newest build files

**TODO Later**

- Make saucelabs connect right every time and then add it to travis CI

**Testing**

- Run any of the scripts with `--git-push-dry-run=true` to keep changes local-only.

**However**, if you run the 'master script' `./scripts/travis/ci.sh` with that flag, it will still push. So don't run that script unless you are a CI server.

The travis build *will not* pass unless we are on driftyco#master (pushing will fail). this is a security measure to make sure that forks of our project can't push things using their own travis servers.