How CircleCI Works
CircleCI integrates with GitHub, GitHub Enterprise, and Bitbucket. Every time you commit code, CircleCI creates a pipeline.
CircleCI automatically runs your pipeline in a clean container or virtual machine, allowing you to test every commit.
Your team is notified if a pipeline fails so issues can be fixed quickly. Automate notifications with our Slack integration.
Passing pipelines are deployed to various environments so your product goes to market faster.
Get the speed and reliability you need when building, testing, and deploying code. Choose the resources you need for optimal performance.
Build software your way using custom job orchestration with workflows. Enable dynamic config to set pipeline parameters, generate config, and more.
Run jobs on Linux, MacOS, or Windows, in our cloud or on your own infrastructure, with access to first-class Docker support.
First-class Docker support
Run any image from Docker’s public/private registry or other common registries, customizable on a per-job basis. Build Docker images, access Docker layer caching, Compose, and more.
Choose the CPU/RAM you need
Easily configure your compute and memory to fit your team’s specific pipelines. Choose resources that give you optimal performance and increase speed.
Speed up your pipelines with expanded caching options, including images, source code, dependencies, and custom caches. Gain control over cache save and restore points throughout your jobs for optimal performance.
The controls you need to be confident your code is protected. Host in our cloud or on your own infrastructure, LDAP for user management, full-level virtual machine isolation, and more.
Build anything on CircleCI
Save time and resources by using our comprehensive, customizable fleet of CI/CD machines, including Docker containers and VMs for Linux, macOS, Windows, and Arm. For additional control and platform support, create custom execution environments on your own infrastructure.
“We successfully migrated both repos and see phenomenal performance improvements, especially when we leverage caching! Our project’s build times went from roughly 2:30 minutes to 1:30 (without cache) and 0:50 (with cache).”
“Today’s experience on @circleci 2.0: my setup was so fast I had to explicitly wait for elasticsearch to start properly before running tests.”
“Build time dropped from 13 minutes to just over 2 minutes after moving to @circleci 2.0 and enabling caching. Great end to the week!”
“Workflows + Docker caching are great with CircleCI 2.0. I’m pumped about what we can do with this! Our Docker build times have gone from ~12 minutes to less than 2 minutes on CircleCI. Fan-freaking-tastic.”
Senior Software Engineer at CrateJoy
“I wasn’t convinced Jenkins was worth the effort. With CircleCI there were none of the headaches I’d experienced before. Everyone who joins our team picks up CircleCI very quickly. It’s always a positive experience.”
CTO at Pingboard