Skip to content

Commit 0a9c246

Browse files
committed
fix 23 - '~' added
1 parent 628791a commit 0a9c246

File tree

3 files changed

+1
-1
lines changed

3 files changed

+1
-1
lines changed

PDF/thesis.pdf

23 Bytes
Binary file not shown.

thesis/projekt-01-kapitoly-chapters.tex

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ \section{Continuous Integration}
2828

2929
Continuous integration (CI) has a key role in the software development process consisting of a few certain unavoidable steps which will be described later in upcoming sections. CI is believed to be an effective way to integrate the source code faster and certify the result of such cooperation, hence an important component of modern software parallel development environments~\cite{ResultsOfCIbuild}. Everything begins at the moment, when one developer who has made changes in a source code of the software product is trying to commit them into the software product. The process of continuous integration has begun at this point and lasts until feedback is sent back to the developer. These stages of continuous integrations are proceed every time after the CI server has detected a change in a version control repository. This automation has a lot of benefits which are necessary to keep the software product without any kind of defects. Many of them are detected in time and reported back to the developer as a corrupted source code. Not a few developers may think that the continuous integration is only about compiling a source code and launching tests. In the next sections, we will present the steps of the continuous integration and describe these individual phases in detail.\\
3030

31-
To imagine the process, there is an illustration about the components and their connections within the process of continuous integration in Figure~\ref{fig:cocis}. The image illustrates situation when \textit{Developer 1} commits changes to the version control repository. The CI server detects this change and provides a feedback about the change back to the \textit{Developer 1}. The \textit{Developer 1} can review informations regarding the change that he made in the given feedback, e.g. tests results.
31+
To imagine the process, there is an illustration about the components and their connections within the process of continuous integration in Figure~\ref{fig:cocis}. The image illustrates situation when \textit{Developer~1} commits changes to the version control repository. The CI server detects this change and provides a feedback about the change back to the \textit{Developer~1}. The \textit{Developer~1} can review informations regarding the change that he made in the given feedback, e.g. tests results.
3232

3333
\begin{figure}[H]
3434
\centering

thesis/projekt.pdf

23 Bytes
Binary file not shown.

0 commit comments

Comments
 (0)