What is the constant propagation in DevOps?
We explain to our
previous educational program in this series the meaning of the word
"continuous delivery".
The continuous
delivery is an automatic pipe to deploy with automatic and manual doors, while
the continuous delivery is a continuous delivery pipeline without manual doors
between them.
Therefore, the
continuous publication does not have to be a "production version".
But the code is released in production and silenced with the Toggle function.
Once ready, the manipulation function is activated.
These functions avoid
the risk of failure of a function in production by stopping the publication
function in production.
This option also
allows you to enable the function for a particular user group, a specific
geography, a specific client site or even internal staff for an initial review
and comments.
transcription:
Just before the
previous video, we knew the approach to continuous distribution and its
benefits.
In this section, tell
us about the continuous implementation and its differences with continuous
delivery. We will also understand the importance of continuous testing and
continuous testing pipelines in DevOps.
Here, I would like to
introduce another term of DevOps, which is continuous publication, which should
not be confused with continuous delivery, since the abbreviated form of each CD
is.
As we already know,
continuous delivery or CD-ROM is the process of providing software or software
updates for production in small increments, which ensures that the software can
be distributed at any time during production.
It is an automatic
pipe to deploy with automatic and manual doors.
Let's now go to the
constant publication.
Continuous deployment
is also a continuous conduit for delivery, but without any manual gate between
them. I mean, there are no manual doors or manual interventions, the initial
code is respected until the code is in production.
This image will show you the continuous deployment channel.
As you can see in
this diagram, it looks like a continuous delivery pipe, there will be a
compilation engine followed by code registration, automated assembly,
compilation, unit testing, publication and other automation tests until
"production deployment".
I would not describe
this as a "production output" but a production publication, which I
will explain in a moment.
Therefore, there are
no manual test steps or manual approval valves or, in other words, no manual
intervention.
This occurs mainly in
a mature organization and in the case of delivery or updating of mature
products. The practices of DevOps are very well established, so the automatic
supply is sufficient to support the quality, manual tests and quality controls
are not necessary.
However, the change
of characteristics is necessary for continuous implementation, even if it is
available in both directions: i, e, continuous delivery and continuous
implementation, and must adapt to the continuous implementation channel.
Changing functions
helps to avoid the risk of production failure by disabling the functionality
published in production. Therefore, this brand indicator ensures that all
functions published in the production can be enabled or disabled according to
the requirements and, therefore, should not be issued immediately to the end
users.
As mentioned above,
continuous publication should not necessarily be a customer problem, but a
"production publication". This option is used for continuous
publication in the publication of timed functions.
For example, the
offer of value-added services of the mobile operator to customers can be sent
to customers until Christmas through the production method of continuous
deployment, at any time, so that the functionality of the service or value package
aggregate remains active and open at Christmas or midnight. New year, etc.,
through the function switch.
This function can be
opened in production during work or sleep hours and can be used safely by end
users later in the day, after making sure they work properly.
Basically, the icon /
function is similar to production, but the icon does not run until the time
runs out or the team decides to change the code or function.
This option also
allows you to enable the function for a group of users
