Today we are officially launching our new free plan. The new and improved free plan now includes private orbs, self-hosted runner, flaky test detection, Docker Layer Caching, and upgraded resource classes for all executors. It also includes a concurrency limit of 30 (upgraded from 1). We want our free offering to be the best any developer can get, period. Check out our announcement post and ask any questions you have in this thread!
@dorianmariefr I’d love some more insight into where the sticking points are with rspec. Is there something in particular that’s difficult or just in general?
A new free plan include Docker Layer Caching , but a testing with a build log on
- setup_remote_docker:
docker_layer_caching: true
Allocating a remote Docker Engine
Requesting version: default
Specified using docker layer caching, but it is only available for Performance Plan.
Upgrade to Performance Plan to use docker layer caching.
I’m on the free tier and despite having docker layer caching enabled in my config.yml, I still get the message:
Allocating a remote Docker Engine
Requesting version: 20.10.11
Specified using docker layer caching, but it is only available for Performance Plan.
Upgrade to Performance Plan to use docker layer caching.
Any suggestions on what to do? Would love to try this out.
You need to send a message to the support team as it seems that accounts have been set up with both this feature and the right to run self-hosted runners are still disabled.
I had the same problem and it took a day or 2 to resolve.
Hi everyone! You should not need to open a Support ticket to have access to Docker Layer Caching on the free plan. It should be available by default. If you have problems, you should definitely let us know so we can fix it.
Well having posted the issue here (see a few messages back). I contacted support and they fixed an issue with my account that was created about a month ago. As part of the email reply, the following was stated.
“There are some cases where the features are not enabled by default due to a bug on our end. I have enabled Docker Layer Caching and Runners”.
Thanks for the clarification @rit1010! This should be a small subset of folks affected by this bug, but you should definitely contact support if you see it.