CI/CD & Docker

What is continuous delivery

What is continuous delivery

 Continuous integration (CI) and continuous delivery (CD) embody a culture,

set of operating principles, and collection of practices that enable application
development teams to deliver code changes more frequently and reliably.

 The implementation is also known as the CI/CD pipeline.

 CI/CD is one of the best practices for devops teams to implement.

 It is also an agile methodology best practice, as it enables software

development teams to focus on meeting business requirements, code quality,
and security because deployment steps are automated.
Continuous Integration

 Continuous integration is a coding philosophy and set of practices that drive

development teams to implement small changes and check in code to version
control repositories frequently.

 Because most modern applications require developing code in different

platforms and tools, the team needs a mechanism to integrate and validate
its changes.

 The technical goal of CI is to establish a consistent and automated way to

build, package, and test applications.
Continuous Integration

 With consistency in the integration process in place, teams are more likely to
commit code changes more frequently, which leads to better collaboration
and software quality.
Continuous Delivery

 Continuous delivery picks up where continuous integration ends.

 CD automates the delivery of applications to selected infrastructure

environments.

 Most teams work with multiple environments other than the production, such
as development and testing environments, and CD ensures there is an
automated way to push code changes to them.
DevOps

 The term DevOps is a combination of two words namely Development and

Operations.

 DevOps is a practice that allows a single team to manage the entire

application development life cycle, that is, development, testing,
deployment, operations.

 The aim of DevOps is to shorten the system’s development life cycle while
delivering features, fixes, and updates frequently in close alignment with
business objectives.
DevOps Lifecycle
Continuous Development

 This is the phase that involves ‘planning‘ and ‘coding‘ of the software.

 The vision of the project is decided during the planning phase and the
developers begin developing the code for the application.

 There are no DevOps tools that are required for planning, but there are a
number of tools for maintaining the code.

 The code can be written in any language, but it is maintained by using Version
Control tools. Maintaining the code is referred to as Source Code
Management.
Continuous Integration

 This stage is the heart of the entire DevOps life cycle.

 It is a software development practice in which the developers require to

commit changes to the source code more frequently.

 This may be on a daily or a weekly basis. Every commit is then built and this
allows early detection of problems if they are present.
Continuous Integration

 Building code not only involves compilation but it also includes code review, unit
testing, integration testing, and packaging.

 The code supporting new functionality is continuously integrated with the existing
code.

 Since there is continuous development of software, the updated code needs to be

integrated continuously as well as smoothly with the systems to reflect changes to
the end-users.

 Jenkins is a very popular tool used in this phase.

Continuous Monitoring

 This is a very crucial stage of the DevOps life cycle where you continuously
monitor the performance of your application.

 Here vital information about the use of the software is recorded. This
information is processed to recognize the proper functionality of the
application.

 The system errors such as low memory, server not reachable, etc are resolved
in this phase.
Continuous Monitoring

 The root cause of any issue is determined in this phase.

 It maintains the security and availability of the services.

 Also if there are network issues, they are resolved in this phase.

 It helps us automatically fix the problem as soon as they are detected.

 This practice involves the participation of the Operations team who will
monitor the user activity for bugs or any improper behavior of the system.
DevOps & CI/CD

 DevOps is a software development approach which involves continuous

development, continuous testing, continuous integration, continuous
deployment, and continuous monitoring of the software throughout its
development lifecycle.

 This is the process adopted by all the top companies to develop high-quality
software and shorter development lifecycles, resulting in greater customer
satisfaction, something that every company wants.
DevOps & CI/CD

Continuous integration and continuous delivery require continuous testing

because the objective is to deliver quality applications and code to users.

Continuous testing is often implemented as a set of automated regression,

performance, and other tests that are executed in the CI/CD pipeline.
Video Links

 https://www.youtube.com/watch?v=5Eqz8hm3SVQ&feature=emb_logo

 https://www.youtube.com/watch?v=scEDHsr3APg
Docker for DevOps

 Docker is a platform that turns out to be a perfect fit for the DevOps
ecosystem.

 It is developed for software companies that are struggling to pace up with the
changing technology, business, and customer requirements.

 The benefits Docker offers to the DevOps environment has made it an

irreplaceable tool in the toolchain
Docker for DevOps

 The reason for Docker being soo good for DevOps is its benefits and use cases
of containerizing the applications that support the development and quick
release.

 DevOps is primarily used to overcome 'Dev' and 'Ops' problems, and Docker
seems to solve most of them, with the main one being that it can work on any
machine.

 Thus, it allows all the teams to collaborate and work effectively and
efficiently.
Docker for DevOps

 Docker allows you to make inevitable development, production, and staging

environments, thereby providing you seamless control overall changes.

 If you want to return to the previous version, you can do that anytime, as all
the environments become more alike.

 Docker guarantees that if a feature is functioning in the development

environment, it will work in the production and staging environment as well.
Docker for DevOps

 One of the biggest benefits of using Docker with DevOps is that developers,
testers, and system admins all use it.

 For instance, developers can use Dockerfiles to create Docker images on local
computers and run them.

 The system administrators can use the same Docker images to make updates
and stage the production environments.

 Thus, you can create stable environments for development, production, and
staging; this approach offers several benefits.
Benefits of using Docker with DevOps

 You get a high level of control over all the changes because they are made
using Docker containers and images. Thus, you can return back to the
previous version whenever you want to.

 With Docker, you get a guarantee that if a feature is working in one

environment, it will work in others as well.

 Docker, when used with DevOps, simplifies the process of creating application
topology embodying various interconnected components.
Benefits of using Docker with DevOps

 It makes the process of load balancing configuration easier with Ingress and
built-in service concepts.

 It enables you to run CI/CD using them, which is more comfortable to use
when compared to just using it with Docker.