Continuous Integration & Deployment Jaime Arias December 2, 2020 

OVERVIEW CONTINUOUS INTEGRATION At every push, run a set of scripts to build, test, and validate the code changes. CONTINUOUS DELIVERY Extension of CI to automate the release process. Deploy the application can be done at any point of time by clicking on a button. CONTINUOUS DEPLOYMENT It goes one step further than continuous delivery. Every change that passes all stages of the production pipeline is released to the customers. It does not require human intervention at all. 2 CI CD CD 

Q: Is the latest version deployed? A: I deployed animated gif support to production. Q: So animated gif support is released? A: The animated gif release is deployed. Q: ... 3 

OVERVIEW 4 

OVERVIEW 5 

● Add a file at the root path of the repository. ● Define the scripts you want to run in the file. ● Once you push your commits, Gitlab detects the file and run the scripts with the tool called . ● Enable the Gitlab Runners in the project. Gitlab CI/CD Pipeline 6 

Gitlab CI/CD Pipeline 7 

Gitlab CI/CD Pipeline 8 

GITLAB-CI.YML 1 9 

● Docs: https://docs.gitlab.com/ee/ci/yaml/README gitlab-ci.yml 10 

Example 2 11 

● https://depot.lipn.univ-paris13.fr/training/ci Example 12 

COVERAGE 2.1 13 

● Docs: https://docs.gitlab.com/ee/user/project/merge_requests/test_covera ge_visualization.html Example 14 

BADGES 2.3 15 

● Docs: https://docs.gitlab.com/ee/user/project/badges.html ● Pipeline Status: https://depot.lipn.univ-paris13.fr/%{project_path}/badges/%{default_br anch}/pipeline.svg ● Coverage Report: https://depot.lipn.univ-paris13.fr/%{project_path}/badges/%{default_br anch}/coverage.svg Badges 16 

PACKAGE & PUBLISH 3 17 

● URL*: https://registry.lipn.univ-paris13.fr/ ● kaniko: https://github.com/GoogleContainerTools/kaniko#running-kaniko-in-docker ● Helper: https://depot.lipn.univ-paris13.fr/arias/docker-publisher LIPN Registry 18 

19