Within the past few weeks, there is no longer a default ruby installed in the base Docker images. This is slowing down Travis builds by a bunch (the rvm line) - Think we can't really change that number too much besides give feedback to TravisCI.
I think Nick and you pointed out that the biggest cost and probably the biggest savings can be obtained from
That script used to be much simpler -- a shell script. Over time it has gotten quite complicated and become a ruby script. A month or two ago I wanted to remove something that was run twice, but it was too difficult and easier to just punt. Wish I remembered more about what I thought needed to be tweaked.
I still feel the
git ruby gems are a problem, but Nick is probably right that with the amount of change, the
git update route is probably quicker.
If we are splitting out various repos, it would seem we could reduce the number of necessary gems.
I wonder if our database setup could be simplified. For many gems, we do not setup a database, but for others, it may be our issue. Seeding is still quite slow and very query intensive.
Don't think Coveralls is a big time sink. Curious about just getting that data from CodeClimate and not using coveralls.