This article provides System Administrator’s with an overview of CircleCI 2.0 installation, features, environments, and architecture in the following sections:
- Installation Options
- Customer Use Cases
- Basic Features
- Build Environments
CircleCI is a modern continuous integration and continuous delivery (CI/CD) platform. CircleCI is installable inside your private cloud or data center and is free to try for a limited time.
CircleCI 2.0 provides new infrastructure that includes the following improvements:
- New configuration with any number of jobs and workflows to orchestrate them.
- Custom images for execution on a per-job basis.
- Fine-grained performance with custom caching and per-job CPU or memory allocation.
If you are a user or developer, refer to Sign Up and Try CircleCI to get started with the hosted application.
There are three basic ways to install CircleCI in your invironment (AWS is currently required for each option):
- A single-box installation, suitable for trials and small teams
- A clustered installation, suitable for production use for most teams
- A highly-available configuration (if supported by your license) to meet higher uptime requirements
Customer Use Cases
Coinbase runs CircleCI behind their firewall for security and reliability. The Coinbase case study report reveals that using CircleCI reduced their average time from merge to deploy in half, reduced operations time spent on continuous integration maintenance from 50% of one person’s time to less than one hour per week, and increased developer throughput by 20%.
Fanatics increased their team efficiency by 300% with CircleCI. See the Fanatics case study report.
CircleCI enables Cruise Automation (a subsidiary of GM) to run many more simulations before putting code in a road test, see the Cruise case study report.
Refer to the CircleCI Customers page for the complete set of case studies for companies large and small who are using CircleCI.
After a software repository in GitHub or GitHub Enterprise is added as a project to the CircleCI application, every new commit triggers a build and notification of success or failure through webhooks with integrations for Slack, HipChat, Campfire, Flowdock, or IRC notifications. Code coverage results are available from the details page for any project for which a reporting library is added.
CircleCI may also be configured to deploy code to all major platforms, including the following:
- AWS CodeDeploy
- AWS EC2 Container Service (ECS)
- AWS S3
- Google Container Engine (GKE)
Other cloud service deployments can be easily scripted using SSH or by installing the API client of the service with your job configuration.
Contact us at Support to request a trial license.
By default, CircleCI 2.0 Builder instances automatically provision containers according to the image configured for each job in your
CircleCI consists of two primary components: Services and Builders. Services run on a single instance that is comprised of the core application, storage, and networking functionality. Any number of Builder instances execute your jobs and communicate back to the Services. Both components must access your instance of GitHub or GitHub Enterprise on the network as illustrated in the following architecture diagram.
The machine on which the Service instance runs must not be restarted and may be backed up using built-in VM snapshotting. Note: It is possible to configure external data storage with PostgreSQL and Mongo for high availability and then use standard tooling for database backups, see Adding External Database Hosts for High Availability. DNS resolution must point to the IP address of the machine on which the Services are installed. The following table describes the ports used for traffic on the Service instance:
|End Users||80, 443||HTTP/HTTPS Traffic|
|Builder Boxes||all traffic / all ports||Internal Communication|
|GitHub (Enterprise or .com)||80, 443||Incoming Webhooks|
The Builder instances run without storing state, enabling you to increase or decrease containers as needed. To ensure that there are enough Builder machines running to handle all of the builds, track the queued builds and increase the Builder instance machines as needed to balance the load.
Each machine on which the Builders are installed reserves two CPUs and 4GB of memory for coordinating builds. The remaining processors and memory create the containers. Larger machines are able to run more containers and are limited by the number of available cores after two are reserved for coordination. The following table describes the ports used on the Builder instances:
|End Users||64535-65535||SSH into builds feature|
|Administrators||80 or 443||CircleCI API Access (graceful shutdown, etc)|
|Services Box||all traffic / all ports||Internal Communication|
|Builder Boxes (including itself)||all traffic / all ports||Internal Communication|
CircleCI uses GitHub or GitHub Enterprise credentials for authentication which, in turn, may use LDAP, SAML, or SSH for access. That is, CircleCI will inherit the authentication supported by your central SSO infrastructure. The following table describes the ports used on machines running GitHub to communicate with the Services and Builder instances.
|Services||80, 443||API Access|
|Builder||80, 443||API Access|