Add official support for R
The R programming language is a rapidly developing language which gained lots of new users in the last years. Coming from the statistical field, its scope has expanded nowadays. Especially the usage in an academic context increased in the last years. R is also used for writing books, creating professional reports, developing UI applications or performing machine learning tasks. Organizations like ropensci or r-lib are great examples of immense open-source effort to advance the R community. Besides these, many developers started developing packages (> 10k open-source packages exist) in the last years and see the need for a CI testing suite. Until now, there is only support for R on Travis CI. I see a lot of advantages in how Circle CI runs builds compared to Travis CI. Hence I would love to see official R support for Circle CI. Among others, this additions would result in reduced build times due to the existence of a cached docker image. Furthermore, having a second CI provider for the R community would give the R community more flexibility regarding their CI provider choice and also put some load off from Travis CI. There have been recent efforts to optimize the support for Circle CI within the R community. Examples are packages like tic or the API-client package circle. CCI-I-1221
Docker Layer Cacheing optimization: Docker layer affinity for volumes
I'm currently doing a lot of work that builds a Docker image using Docker Layer Cacheing, but I'm doing so in a branch. At the same time, several other developers are also working in the same project but the Dockerfile for this image isn't yet merged. As a result, their Docker remote engines are acquiring volumes so starve my branch of cached images. This makes working in a branch really slow because it seldom chances on a volume that has the image layers available. If jobs had some kind of affinity for mounting volumes that had available image layers, this would improve branched development a ton! CCI-I-800
Please add packaged Clojure (with CLI tools) pre-built Docker images
Circle provides pre-build Docker images for lein and boot users but does not provide an image with the Clojure CLI tooling (the clj command) provided in the first-party Clojure packages. We are switching from Lein to the new first-party tooling (deps.edn and cognitect-labs/test-runner) for some projects and it would be great to have the clj tool available in a pre-built image so we don't have to install it explicitly each time. CCI-I-256
Support for ARM based Docker images.
An ARM-based executor for ARM-based Docker images would allow Raspberry Pi development as well as other ARM software. CCI-I-900
Support dotnet core docker images
It would be good to have docker images for dotnet core applications out of the box. CCI-I-1134
Cache Docker images on Docker executor
Currently, DLC only applies to the actual building of Docker images within jobs. It'd be nice to enable DLC for the actual spin up of environment Docker images, since those tend to vary wildly from just a few seconds to a few minutes. Enabling DLC will allow for consistently fast spinup of environment. CCI-I-1004
Offer cimg/redis Convenience Image
This is a request to offer a cimg/redis convenience image in direct replacement for the legacy circleci/redis image.
Support Major Version Tags
For Docker Convenience Images, support major version tags, such as cimg/node:15 for the Node.js image.
Re-introduce "latest" tags for next-gen convenience images
Customers want to always be using the latest versions of a major release (e.g., 12.x) without having to explicitly specify/change the version each time in the configuration.
Simplify import of signing certificates on macos executors
Apple makes it non-trivial to sign OS X applications and installers. As it stands, getting signing certificates from one development machine to another is an undertaking; getting them onto a macos executor is very difficult, especially if you're not building an XCode-based project (e.g. Electron apps), but increased security restrictions on each release of OS X makes it mandatory if you want to distribute your application. Providing a relatively easy way to import the signing certificates into a project's settings (as well as documentation on how to export the certificates properly) would be enormously helpful when building non-XCode applications and installers. CCI-I-797