I removed Travis because I started using Circle CI, which IMO is a much better product. A lot of hacky stuff I was doing on Travis (caching bundled gems to avoid ~5 minute bundle times on each run) is done for you on Circle CI, and the interface is a lot less buggy. Unfortunately, I was wrong when I assumed it was free for public repos.
I can dig up the old .travis.yml file in the repo if it'll help get things back on track, but we'll have to remove some of the bundle caching since it's currently using my personal AWS account to upload bundles, and that's probably not the best idea going forward.
Thanks for the follow-up! I'm pretty agnostic on the CI service itself -- my goal is just to have some CI check so that new pushes don't break existing deployments/ops.
Just to follow up on this --
I removed Travis because I started using Circle CI, which IMO is a much better product. A lot of hacky stuff I was doing on Travis (caching bundled gems to avoid ~5 minute bundle times on each run) is done for you on Circle CI, and the interface is a lot less buggy. Unfortunately, I was wrong when I assumed it was free for public repos.
I can dig up the old .travis.yml file in the repo if it'll help get things back on track, but we'll have to remove some of the bundle caching since it's currently using my personal AWS account to upload bundles, and that's probably not the best idea going forward.