Bring your own agent/runner/worker machine.
complete
B
Brian Kruger
If you implemented CCI-I-709, then from there, additional privileges could be added for CCI to launch machines in private accounts. CCI still runs the master servers, but the agent/slave/worker could run in customer's account which would also allow access to internal services that a customer may not want to give external access (security checks, code analysis tools, artifact storage, etc.) The customer becomes responsible for machine costs and items like additional memory, etc. are a burden on the customer, but the customer doesn't need to maintain a master/onprem version.
CCI-I-995
J
Jonatan Castro
you would expect to have this in every plan, not just on "Scale".
With this functionality, the company ends up paying for the processing (EC2, on premise server, etc)... so this is actually savings for CircleCI. It's just annoying we need to upgrade to get this feature.
Buildkite gives you this in every plan.
Alexey
Merged in a post:
Self-host runner for cloud CircleCI
B
Bean
Hi Team,
I'm wondering is there any possible way to build on self-host runner with cloud CircleCI?
Alexey
complete
Alexey
We are excited to announce the availability of CircleCI runners! Check out the product page for runners here:
You can find the overview documentation for runners here:
A
Andmar
I was expecting that would be a standard feature since this works perfectly on Azure DevOps.
K
Kristoffer Bakkejord
GitLab CI and Azure Pipelines also supports this.
T
Tim Macfarlane
Worth noting that some other competitors do this:
BuildKite: https://buildkite.com/features
T
Tim Macfarlane
We would certainly like to use this sort of functionality. We operate on premises hardware that we'd like to deploy some of our services to, and for that we'd like to run build agents behind our firewall, but still be able to use cloud-based CircleCI for build management, logs, etc.