GitLab
Pipeline:
* Group of jobs executed in Stages.
* All of the jobs executed in parallel in stage.
* if all jobs succeed, pipeline move to next stage.
* if any one job failed, next stage is not executed.
Types of Pipeline:
* CI Pipeline
build and test stages defined (.gitlab-ci.yml)
* Deploy Pipeline:
define in .gitlab-ci.yml. Flow of deploying code to server thru various stages.
* Project Pipeline:
Specially for microservices.
Cross project CI depencies, triggered via API.
GitLab Architecture:
* GitLab Server and atleast one GitLab Runner.
* Runner is the one will start the job.
* Project Setting -CICD -
* GitLab Runner is automatically provided by GitLab Server.
* We can also configured our own runners.
Why GITLab CI:
* Simple Architecture
* Docker first approach.
* Pipeline as code.
* Merge request with CI support.
Eg. Build file location:
/builds/kumarvinothjoseph/spring-boot-integration-watch-directory/target/spring-integration-monitorfolder-filereading-0.0.1-SNAPSHOT.jar
* Group of jobs executed in Stages.
* All of the jobs executed in parallel in stage.
* if all jobs succeed, pipeline move to next stage.
* if any one job failed, next stage is not executed.
Types of Pipeline:
* CI Pipeline
build and test stages defined (.gitlab-ci.yml)
* Deploy Pipeline:
define in .gitlab-ci.yml. Flow of deploying code to server thru various stages.
* Project Pipeline:
Specially for microservices.
Cross project CI depencies, triggered via API.
GitLab Architecture:
* GitLab Server and atleast one GitLab Runner.
* Runner is the one will start the job.
* Project Setting -CICD -
* GitLab Runner is automatically provided by GitLab Server.
* We can also configured our own runners.
Why GITLab CI:
* Simple Architecture
* Docker first approach.
* Pipeline as code.
* Merge request with CI support.
Eg. Build file location:
/builds/kumarvinothjoseph/spring-boot-integration-watch-directory/target/spring-integration-monitorfolder-filereading-0.0.1-SNAPSHOT.jar
Comments
Post a Comment