What is continuous
delivery in DevOps?
The continuous integration was explained in detail in the
last tutorial. Here we will see continuous delivery in DevOps.
Continuous delivery is the important process of delivering
software / production updates in small increments, which guarantees that the
software can be launched at any time. Through this DevOps approach, the team
will always be ready to "connect at any time" for production.
Therefore, the continuous delivery is a pipeline or a life
cycle of the code. The code that has been developed or updated recently by the
software team is tested in different stages, either manually or automatically,
manually and automatically. Production
The main objective and objective of the continuous delivery
is to create, test and transfer the client fairly quickly and more frequently,
in short sessions.
Below you will find
the advantages of the CD.
·
Greater number of births.
·
Reduces the risk of production failure.
·
Reduce manual work.
·
Increase confidence in the team.
·
It allows the team to automate everything.
·
It allows a faster return.
Text:
We have completed parts 1 and 2 of this series of
conferences and are currently in Part 3, Part 2.
In Section 1, we studied continuous integration, an
automatic process task in DevOps practice, where we realized that continuous
integration is an ongoing process to integrate each developer code into a
central repository. And verify your integration successfully with the automated
unit tests and the module. .
We also study the
benefits of IC.
Now, let's understand the continuous delivery, which is
another important exercise in DevOps practice.
We know that the main objective of DevOps is to provide small
increases in value to customers continuously.
Therefore, in line with this objective, the continuous
delivery, the CD is very similar to the team that is always ready to
"connect at any time" production, instead of our previous model,
which is only offered in the times of specified delivery. Date and paste to
this date only.
Therefore, the continuous delivery is a pipeline or a life
cycle of the code. The code that has been developed or updated recently by the
software team is tested in different stages, either manually or
automatically, manually and automatically. Production
The main objective and the main objective of continuous
delivery is to create, test and send the customer quickly and more frequently.
You know quickly and often refers to a few hours in DevOps.
In summary,
continuous delivery is the method of delivering programs in short sessions.
Therefore, of course, the CD wants to deliver value to the
customer frequently, which reduces costs, increases delivery speed, increases
reliability and reduces the risk of delivering large portions of code.
Continuous delivery is an automated implementation channel,
therefore, obviously,
# 1. Increase the number of births
# 2.A computer CD is a small short cycle in which it takes a
few hours. Because the compact disc is a small and repetitive display, it
eliminates the greatest risk of production failures.
# 3. Unless human intervention requires it, everything, from
start to finish, is automated. Thus, many crafts are reduced.
# 4.Continuous delivery generates confidence in the team,
will always be willing to "deliver the production", its spirit will
be constantly linked to the quality and production speed expected.
# 5.Continuous delivery allows and enriches the development
and processes to automate the whole process, including the activities and
operations of development, launch, compilation, test modules, deployment,
identification of the infrastructure and environment settings in the form of
code , performance, user interface, etc.)
# 6. No less important, the continuous delivery, being a
short implementation cycle, helps the team to obtain a faster delivery return,
which not only comes from the development environment, but also from the
production environment. Stress or BAU, as usual for the team.
