CircleCI is a continuous integration and continuous delivery (CI/CD) platform that automates the software development process. CI/CD is a set of best practices and tools that enable software developers to regularly and automatically test and deploy their code changes. The goal is to catch bugs early in the development process, ensure code quality, and streamline the release pipeline.

1. Introduction to CircleCI
Abhishek Tiwari
Software Consultant
DevOps Competency

2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
 Punctuality
Join the session 5 minutes prior to the session start time. We start on
time and conclude on time!
 Feedback
Make sure to submit a constructive feedback for all sessions as it is very
helpful for the presenter.
 Silent Mode
Keep your mobile devices in silent mode, feel free to move out of session
in case you need to attend an urgent call.
 Avoid Disturbance
Avoid unwanted chit chat during the session.

3. 1. What is CircleCI
 Features
2. Benefits of CircleCI
3. Architecture
4. Executers
5. Demo

4. What is CircleCI
 CircleCI is a cloud based continuous integration and continuous delivery platform that can be
used to implement DevOps practices.
 It allows developers to set up automated workflows that trigger on code changes, enabling them
to quickly and consistently test and deploy their applications.
 Overall, CircleCI helps development teams streamline their software development process,
improve code quality, and accelerate the delivery of new features and updates to their
applications.

5. Features
 Automated Builds
 Testing Automation
 Continuous Deployment
 Customizable Workflows
 Cloud-based Service

6. Benefits
 Organizations choose CircleCI because jobs run fast and builds can be optimized for speed.
CircleCI can be configured to run very complex pipelines efficiently.
We can use CircleCI to:
 SSH into any job to debug your build issues.
 Set up parallelism in your .circleci/config.yml file to run test jobs faster.
 Configure caching with two simple keys to reuse data from previous jobs in your workflow.
 Configure self-hosted runners for unique platform support.
 Use orbs, reusable packages of configuration, to integrate with third parties.
 Use pre-built Docker images in a variety of languages.

7. Architecture

8. Executers
 An executor defines the underlying technology or environment in which to run a job, and which
image to use to best-suit your project
 CircleCI provides four Execution environments.
 Docker
 Linux VM (virtual machine)
 MacOS
 Windows

10. DEMO