CircleCI Ideas

Bring your own agent/slave/worker machine.

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. 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 15 2019
  • New
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    20 Jan 10:03am

    I was expecting that would be a standard feature since this works perfectly on Azure DevOps.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    2 Jul, 2019 03:18pm

    GitLab CI and Azure Pipelines also supports this.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    30 Apr, 2019 02:06pm

    Worth noting that some other competitors do this:

    BuildKite: https://buildkite.com/features

    CodeFresh: https://codefresh.io/docs/docs/enterprise/behind-the-firewall/

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    30 Apr, 2019 02:04pm

    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.