What is the ongoing integration of DevOps?
So far, we have
covered the first and second parts of this topic in our previous sessions,
which are currently listed in Part III.
Up to Part 2, we
cover the people side and DevOps, a collaboration and we focus on a common
goal, a common mindset and shared thinking within the team contributing to the
achievement of DevOps goals. During our last educational program, we learned
how to develop cooperation in DevOps.
 |
| DevOps Integration |
Text:
How are the goals of DevOps achieved through these principles?
We have studied the
importance of controlling emission and automation and providing small increases
in value and benefits to customers.
What is DevOps collaboration and how can it be done?
So far, we've talked
about people and aspects of the DevOps process, that is, cooperation and focus
on a common goal, a common mindset and reflection within the team that
contribute to achieve the goal of DevOps. , Making possible the publication of
DevOps.
These are continuous
integration, continuous delivery and deployment, and continuous testing.
Continuous
Integration -> CI -> Process Set -> Pipeline Construction / CI
Continuous
Integration, referred to briefly as "CI" in DevOps, is an important
process or set of processes defined as part of a pipeline called Pipeline
Creation or CI Pipeline.
We know that in
DevOps practice, we have a unique version of this tool for the development and
operations team, where all are coded as the basic rule of the link, allowing
the team to work in parallel.
Therefore, the
continuous integration of DevOps is nothing more than the integration of the
developer code into the main version of the code in which the version is kept.
There is no limitation on the theme of the symbol that should appear in a day.
Once the developer
has verified their code in the control version, the IC boot process starts
immediately.
The IC process,
1. Merging all the
developer code on the main line,
2. Activate the
construction,
3. Collect the code
and do the compilation and ...
4. Perform unit
tests.
Thus, continuous
integration involves integrating the development blade into a central location
and validating each of its combinations with automated assembly and testing.
