I’m loving it! Refugee from Travis here; Circle is awesome. I hopped straight onto 2.0 and it’s been working well for us. In particular, things that I like:
Explicit cache naming, loading, and saving. It’s super intuitive to make a cache for only specific parts of the build; for a Golang project I can save the build environment and compiled
.afiles for standard-library cross-compilation, without contaminating the cache with project-specific files. It also seems clear how you might use multiple separate caches should the need arise.
Clear separation of infrastructure. Rather than slap-dashing everything together, it’s very nice to grab stuff off the shelf and have ports automatically rigged together. Any
apt-getcommands are no longer allowed in my CI scripting and I love it.
Segmented steps displaying separately in the UI. We have a Travis build that hovers around 80k lines ; this feature is a lifesaver.
Web UI is significantly faster than a snail. I don’t know what on earth other providers are doing, but the Circle UI has pretty-reasonable web performance. Surprisingly rare!
Local builds that are an (almost) exact representation of the remote. Every project inevitably rigs up some ghetto scripting to try & work around cloud CI providers not having this obvious feature; it’s nice to skip this step.
These may or may not be all new in 2.0, sorry. But I’m having a good time