Scribd
Upload
14 views2 pages

DevOps: Continuous Integration & Delivery

The document outlines the fundamentals of DevOps, emphasizing the integration of development and operations teams towards unified goals through collaboration and automation. It discusses three models for adopting DevOps in projects, focusing on team structure, processes, and technology stacks, including tools like Git, Jenkins, and Docker. The DevOps lifecycle is presented as a continuous cycle of coding, integration, testing, deployment, and monitoring.

Uploaded by

varsha.amrutha0512
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
14 views2 pages

DevOps: Continuous Integration & Delivery

The document outlines the fundamentals of DevOps, emphasizing the integration of development and operations teams towards unified goals through collaboration and automation. It discusses three models for adopting DevOps in projects, focusing on team structure, processes, and technology stacks, including tools like Git, Jenkins, and Docker. The DevOps lifecycle is presented as a continuous cycle of coding, integration, testing, deployment, and monitoring.

Uploaded by

varsha.amrutha0512
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

Continuous Integration and Delivery - DevOps :

[Link]
9_shared/overview

Agenda:
-----------
Fundamentals of DevOps
Adoption of DevOps in project
Demo
--------
Why? What? Adoption of DevOps

DevOps = Dev( Dev +QA) + Ops ( Release management, Deployment management, Security,
Infra, Support..)

DevOps combines all the team together towards an unified goals and metrics, this
process driven by automation.

Keywords: Collaboration, Automation

Adoption of DevOps in project:


------------------------------------------
3 aspects of DevOps:

People:
--------------
Team Structure enablement

Model 1: ( As - IS State) Sep Dev and Ops team. Intervention point to bring
collaboration.

Model 2: (Pure DevOps) Single Integrated team with cross functional people

Model 3:( Near DevOps) Sep Ops team. Couple of members from the Ops team working in
the Dev team. DevAppOps

Process:
-------------
Model 1: Dev = Scrum Ops = ITIL ( Information Technology Infrastructure
Library)/ any other process

Model 2:- Dev = Scrum Ops = Kanban (Same PO, but different Product backlog)

Model 3: DevOps = Scrumban ( Same PO, Same PB)

Coding - Repos - Continuous Integration (Build) - Continuous Testing - Continuous


Deployment - Continuous Monitor

Technology:
------------------
[Link] Stack
Code : JAVA

IDE : Eclipse
Repo: Git
Build : Maven
Automation Tool: Jenkins
Unit Testing: Junit
CodeCoverage: Jacoco
Testing: Selenium
Containerization: Docker
Configuration management Tool : Ansible
Infra management Tool : Terraform

2. DevOps Stages: Version Control : SCM : source code management


Continuous Integration (Build)
Continuous Testing ( Functional
and Performance)
Continuous Deployment
Continuous Monitor

Coding -> Repo


Automation tool fetches the code from repo

CI -> CT-> CD -> CM

You might also like