Setup a Continuous Integration system

buckmaxwell / github-issues-ebs

An implementation of evidence based scheduling (EBS) for github issues. This tool will integrate with Github Issues and Google Calendar and help developers and teams to accurately estimate timelines. The tool pairs well with Agile methodologies or can stand alone.

0 stars 0 forks source link

Setup a Continuous Integration system #10

Open erikthiem opened 7 years ago

erikthiem commented 7 years ago

This is just setting up a CI system, not actually doing anything with tests. Possible candidates I have heard of: Jenkins CI, Travis CI I'm not quite sure where this will live. Perhaps in another Heroku app.

@estimate:4h

erikthiem commented 7 years ago

Jenkins

pro: free for non-open-source use, I've used it a bit at work
con: have to setup and maintain our own Jenkins server

Travis

pro: they host it, interface looks nice
con: we have to either open source our project or pay a substantial fee (at least $69/month)

Heroku CI:

pro: integrates well with Heroku
con: $10/month + cost per test (might be bad, as this disincentivizes running tests and frequent deploys)

buckmaxwell commented 7 years ago

Jenkins seems like the best option then as there are some hurdles before we can open source. Looking into Jenkins as a Service to see if we can avoid the trials and tribulations of keeping a test server at 99.99% uptime on our own

buckmaxwell commented 7 years ago

@erikthiem have you looked at Solano CI, Codeship CI, or Semaphore?

https://elements.heroku.com/addons/tddium (solano -- starts at 7/mo) https://elements.heroku.com/addons/codeship (codeship -- starts Free) https://elements.heroku.com/addons/semaphore (semaphore -- starts Free)

buckmaxwell commented 7 years ago

Semaphore seems pretty cool.