Set up CI

[peckjon]

Let's add CI so we don't have to manually build each time.

PUBLISH.md holds the env setup info.

Build script would simply be:

grunt build:image-tagger
grunt build:colorize-photos
grunt build:classify-places
grunt build:deep-fashion
grunt build:deep-style
grunt build:web-page-inspector
grunt build:video-search
grunt build:rss-dashboard
grunt build:sitemap
grunt build:timeseries
grunt build:isitnude
grunt build:video-toolbox
grunt build:video-metadata

@anowell my usual tendency is to add a publish branch but AFAIK you prefer CI to run off master and for us to create a dev or feature-branches instead?

[anowell]

Re-publishing all demos every time seems a bit heavy-handed. :-/ But trying to find the right subset feels a bit complex, so I don't have a better idea at the moment.

Re: master vs publish - I just like the philosophy of "keep master shippable". Plus, the PR workflow works slightly better with that then with a separate publish branch, but if not-deployable stuff is getting into master, switching to a publish branch as an extra gate seems reasonable. (Platform actually uses a prod branch for this purpose, and we try to keep master in sync with test.)