CI Testing

[krambuhl]

If we are implementing lots of testing and automation continuous integration would be a very useful addition, but would have a cost component for private repositories.

Possible Dev Cycle

1. Develop website locally
2. Bump version (via Pre-release/version bump task #22)
3. Push to remote git repo
4. Startup free heroku instance related to git branch
5. Open pull request on Github/Jira

Codeship This is my prefered solution. Lots of built-in integrations to keep dev-ops to a minimum. Would be probably $40-80 a month for private repos.
Travis CI $130 a month for private repos.

[elseloop]

We (CDX) have a Jenkins server that's used for a number of internal & client projects (http://build/ on the network). I would need to check with the internal owners of it (canderson, I think? Maybe Kam.), but I'd assume we could leverage that for this purpose (hard knock on assume). It has great tie-ins with GitHub repos/workflows, so would likely serve our purposes, at least initially, at least for the core project repo.

@stoff, do you have any knowledge of our established Jenkins workflow? I've only ever interacted with it after it was setup by a dot net dude, usually close to or after a launch.