CI: Replace Travis CI with CircleCI #90
Conversation
There was a problem hiding this comment.
This is slightly different from the Travis one in that we don't specify the OTP version.
Maybe that's something we should explore to ensure no breaking changes.
We could probably add 1.11 to this too now that it has been out for a bit.
Everything else looks great.
I agree that this would be useful. However, if we are going to use that pattern then we'll need to use a different set of Docker images as CircleCI only tag their images with the Elixir version (either via |
* Paginator itself only supports Elixir ~> 1.5 * Inch ~> 2.0 only supports Elixir >= 1.7.0
Version 1.11 is the latest generally available release of Elixir.
|
Closing in favour of #100. |
💁 Over time, the performance of the builds run by Travis CI for this repository has degraded to the point where it now can take > 2 hrs for the build matrix for the Elixir and Erlang/OTP combinations that currently exist to setup and finish running. The problem here is not that each test run takes a long time (each job currently takes ~1m30s to execute), it's that Travis takes so long to provide build instances to run the build itself.
See this recent build for an example of this.
Having a such a slow build time is an impediment to contributors and automation alike. Contributors to this project will feel the pain of waiting for their builds to complete. Maintainers will feel the pain waiting for automation like Dependabot package updates to complete. To compound this, Travis CI recently announced changes to their pricing and build credits which affects OSS projects.
💡 To mitigate all of this, I suggest that we move this project to use CircleCI instead. These changes implement that by migrating the existing build from Travis CI to CircleCI.
Feedback on this proposal are very welcome!