Images

It is advised to use convenience images. Adoption would grow when these images would be cached to reduce the time needed for everyone to spin up the environment. Right now spinning up the environment takes between 30 and 60 seconds already. Starting container circleci/mysql:8 image cache not found on this host, downloading circleci/mysql:8 https://circleci.com/docs/2.0/circleci-images/ CCI-I-1345

In the same way customers can create their own custom Docker images for execution ( https://circleci.com/docs/2.0/custom-images/ ), it would be a great feature to have custom AMIs for the machine executor. Just tell us what needs to be pre-installed on these AMIs to run on your system. This is especially useful for: Cutting down build time associated with installing specific dependencies on a clean box Removing complexity associated with installing specific dependencies programmatically CCI-I-998

Open source the repository and build files that are used to create the machine images used by CircleCI.com . This includes the Ubuntu, macOS, and Windows VM images.

It would be amazing to be able to cash the expensive 'brew install' operations. These actions eat a large amount of the "credits", which is exacerbated by the fact that MacOS consumes them at a rate of 5x.

What:Resource classes that introduce higher CPU without additional memory, balancing the credits required accordingly.Why:Current resource class options all step CPU & RAM in ratio of 1:2. Some use cases are heavily CPU bound, but not memory bound, and for various architectural limitations of these 3rd testing tools are not capable of leveraging GPU class machines. Ideally these classes would ahve a ratio of 1:1 or even 2:1 of CPU:MemExample Libraries/Tools benefiting:Visual regression testing tools like https://github.com/americanexpress/jest-image-snapshot have been cited as examples of CPU intensive needs. CCI-I-857

It would be nice if we maintained AMIs with runner pre-installed. This would save customers time when provisioning runners.

When users use an image that does not have ssh or git installed by default, we revert to a "native git client". > Falling back to CircleCI's native git client but the behavior may be different from official git. It looks like this native client is quite old. It would be nice if this native client was a newer version because then it would support a wider range of use cases. CCI-I-795

Sometimes your build isn't CPU or RAM bound, it's disk I/O bound. Have a resource_class option that allows us to buy more IOPS for those cases. CCI-I-674

We would like to build and test services that are not open to the public, and the ability to configure a VPN inside a machine executor would allow us grant access to our services for integration testing. CCI-I-698

Some jobs do not benefit from increased CPU count and/or RAM, but can be dramatically sped up by faster CPU clock-speeds.It would be great if container performance could be adjusted more precisely, meaning CPU count can be increased without increasing RAM, and CPU clock-speed can be increased without doubling the CPU count. There are too many different jobs, so having a list of possible configurations will always make someone unhappy. The best solution would be to be able to configure containers precisely, for example: 2 CPUs 4 Ghz variant 4 Gb of RAM -- or -- 8 CPUs 2 Ghz variant 10 Gb of RAM CCI-I-1092