This document discusses using container-based continuous integration (CI) to provide on-demand build infrastructure. It outlines challenges with traditional CI approaches like long wait times, underutilized resources, and slow onboarding. The proposed solution is to run CI tools and jobs inside containers orchestrated by Kubernetes to provide scalable, on-demand infrastructure. An example case study shows how this approach reduced costs by 50%, improved utilization 12x, and reduced onboarding time by 55% for a client's Jenkins deployment on AWS.

1. ContainerbasedContinuous
Integration(CI) forbuild
infrastructureon-demand
Archana Joshi & KarthikeyanVedagiri
Digital Engineering - Cognizant

2. AboutUs
Director,
Digital Engineering -Cognizant
Associate Director,
Digital Engineering -Cognizant
How many of you have used a pipeline / implemented a pipeline

3. Typical
DevOps
Pipeline Agile Development

4. CI
Components
Infrastructure (24x7)
CI Ecosystem (24x7)
Code
CI PipelineTemplate

5. Can Magic
Happen?

6. Pipeline
Reserved to On Demand
Infrastructure (On Demand)
Using containers
CI Ecosystem (On Demand)
Code
CI PipelineTemplate
Infrastructure (24x7)
CI Ecosystem (24x7)
Code
CI PipelineTemplate

7. Do you face
this?
Developer
Build Engineer
 Why is it taking long for the team to
provide me withCI pipeline?
 Other applications already have it.This
team seems to be very slow. It is affecting
my ability to put into production and my
product owner is not happy
 Why can’t our company adopt DevOps
faster. It will be much easier that way.
 I already have pipeline but I still have to
wait in the build queues. Instantaneous
build seems to be a dream
 I was told to develop CI pipeline only
for 10 apps. Now suddenly ourCIO
wants it to be deployed for all our
applications in his portfolio
 I am already short staffed. I now need
to also get budget approvals for all
the new infrastructure that will be
needed for doing this.
 If only, I had something which will
help me turn this around quickly &
save tedious conversations with my
Infra manager on effective utilization

8. Do you face
this?
DevOps champion
 If only my management understood
that building CI is not simple as Copy
Paste
 Management also wants me to do
Enterprise DevOps where Enterprise
adoption of CI is just the beginning of
journey
 We aim for Enterprise DevOps but our
infra is already under pressure for
utilization and cost
 I need to get this right. No one is
happy about the slow adoption of
DevOps

9. Utilization is less than 5%
Onboarding apps to CI take close to 3-4 weeks
Long waiting times in queues delaying my developer feedback
Numerous no of jobs, slave nodes becoming a maintenance nightmare
Have separate operations teams to manage/administer Jenkins
- customer quotes during DevOps assessments and consulting
In our 100+
DevOps
assessments
we have heard

10. CaseStudy
One of top 5 from the healthcare providers in
USA
Jenkins based CI ecosystem onAWS spanning
across 50 dedicated servers.
Challenges with scalability, utilization and costs.
Took 2 weeks to onboard new applications
(100+ applications)
Can you help us move to a scalable yet
cost effective CI environment?
Before

11. What can I
possibly do to
get anOn
DemandCI ?
We decided to leverage containers

12. But what
exactly are
containers
 A standard unit of software
 Packaged into a lightweightOS
 Contains all that is needed to run software
 Easy to manage, ship and deploy
 Ultrafast and portable
 Preferred choice for hosting microservices

13. Relevance of
containers to
pipeline
 If apps can be run inside containers, So can Jenkins!.
 Run Jenkins inside a containers
 Execute the pipeline inside the scope of a containers
 For every build -> Create – Execute –Terminate – Repeat
Scalable CI ecosystem

14. Continuous
Integration
solution based
on containers
that creates
build
infrastructure
On-Demand
Overall OrchestrationOrchestration of the overall
CI infrastructure
Container
ManagementScalable CI farms spawned
as containers on demand
Containerization
Individual containers
working as CI nodes
CIContinuous Integration Tools
focusing on core CI functions

15. Conceptual SolutionArchitecture

16. CaseStudy
One of our customer from the healthcare industry had Jenkins
based CI ecosystem on AWS spanning across 50 dedicated servers.
In spite of it, had challenges with scalability, utilization and costs.
Currently takes 2 weeks to onboard new applications.
Can you help us move to a scalable yet cost
effective CI environment?
Before
A scalable Jenkins based CI system built on top of Kubernetes
clusters with 10 nodes providing
 50% reduction in costs (from 50 EC2 instances to just 10)
 12x improvement in build farm utilization
 55% reduction in onboarding time for apps.
After

17. Thank You
https://github.com/CognizantOneDevOps
https://www.linkedin.com/in/arcjoshi
https://www.linkedin.com/in/Karthikeyan.vedagiri
Note:The views represented in the presentation are solely of the presenters and do not represent those of the company / clients she is associated with