Difference between revisions of "Migration of the Jenkins CI/CD pipeline into Gitlab CI/CD"
(Created page with "== Description The goal of the DEEP Hybrid DataCloud project [1] is to prepare a new generation of e- Infrastructures that harness latest generation technologies, supporting d...") |
|||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | + | = Description = |
|
+ | The goal of the DEEP Hybrid DataCloud project [1] is to prepare a new generation of e-Infrastructures that harness latest generation technologies, supporting deep learning and other intensive computing techniques to exploit very large data sources. In order to ease and lower the entry barrier for non-skilled scientists, DEEP offers DevOps approach to its users based on Jenkins CI/CD pipeline. Aim of the student project is to migrate existing Jenkins CI/CD pipeline into Gitlab CI/CD. |
||
− | The goal of the DEEP Hybrid DataCloud project [1] is to prepare a new generation of e- |
||
− | Infrastructures that harness latest generation technologies, supporting deep learning and other |
||
− | intensive computing techniques to exploit very large data sources. In order to ease and lower the |
||
− | entry barrier for non-skilled scientists, DEEP offers DevOps approach to its users based on Jenkins |
||
− | CI/CD pipeline. |
||
− | Aim of the student project is to migrate existing Jenkins CI/CD pipeline into Gitlab CI/CD. |
||
− | + | = Tasks = |
|
− | + | * get acquanted with Jenkins and declarative CI/CD pipeline [2]. |
|
− | + | * understand Gitlab CI/CD pipeline and its features [3] |
|
− | + | * understand Docker container technology [4-5] |
|
− | + | * migrate existing Jenkins pipeline into Gitlab CI/CD [6] |
|
− | + | = Requirements = |
|
− | + | * understanding of CI/CD |
|
− | + | * ideally you have knowledge of Docker containers, Jenkins declarative pipeline/Jenkinsfile structure, yaml, Gitlab CI/CD |
|
− | structure, yaml, Gitlab CI/CD |
||
+ | = Contact = |
||
− | == References |
||
+ | [mailto:valentin.kozlov@kit.edu Valentin Kozlov] |
||
+ | |||
+ | = References = |
||
[1] https://deep-hybrid-datacloud.eu |
[1] https://deep-hybrid-datacloud.eu |
||
+ | |||
[2] https://jenkins.io/doc/book/pipeline/jenkinsfile/ |
[2] https://jenkins.io/doc/book/pipeline/jenkinsfile/ |
||
+ | |||
[3] https://docs.gitlab.com/ee/ci/pipelines.html |
[3] https://docs.gitlab.com/ee/ci/pipelines.html |
||
+ | |||
[4] https://www.docker.com |
[4] https://www.docker.com |
||
+ | |||
[5] https://docs.docker.com/develop/develop-images/dockerfile_best-practices/ |
[5] https://docs.docker.com/develop/develop-images/dockerfile_best-practices/ |
||
+ | |||
+ | [6] https://jenkins.indigo-datacloud.eu/job/Pipeline-as-code/job/DEEP-OC-org/job/dogs_breed_det/job/test |
Latest revision as of 15:55, 15 October 2019
Description
The goal of the DEEP Hybrid DataCloud project [1] is to prepare a new generation of e-Infrastructures that harness latest generation technologies, supporting deep learning and other intensive computing techniques to exploit very large data sources. In order to ease and lower the entry barrier for non-skilled scientists, DEEP offers DevOps approach to its users based on Jenkins CI/CD pipeline. Aim of the student project is to migrate existing Jenkins CI/CD pipeline into Gitlab CI/CD.
Tasks
- get acquanted with Jenkins and declarative CI/CD pipeline [2].
- understand Gitlab CI/CD pipeline and its features [3]
- understand Docker container technology [4-5]
- migrate existing Jenkins pipeline into Gitlab CI/CD [6]
Requirements
- understanding of CI/CD
- ideally you have knowledge of Docker containers, Jenkins declarative pipeline/Jenkinsfile structure, yaml, Gitlab CI/CD
Contact
References
[1] https://deep-hybrid-datacloud.eu
[2] https://jenkins.io/doc/book/pipeline/jenkinsfile/
[3] https://docs.gitlab.com/ee/ci/pipelines.html
[5] https://docs.docker.com/develop/develop-images/dockerfile_best-practices/
[6] https://jenkins.indigo-datacloud.eu/job/Pipeline-as-code/job/DEEP-OC-org/job/dogs_breed_det/job/test