GitLab Continuous Integration (CI) & Code Review
Details
After an Introduction to Git and GitLab as well as to clean and reusable code, the NOWA workshop workflow continues with a workshop on GitLab CI and Code Review.
Continuous Integration (CI) is an automated testing of your code which will always be triggered if changes are to be integrated in the main, shared version of your project (i.e., the main branch). It helps to find bugs early and thus to avoid major damage of your code. Also, by running automated tests regularly, you save time in contrast to do it manually.
A code reviewing process usually involves the main developer of the code and another person who checks the code regarding understandability, tests, documentation, and security. Communication between main developer and code reviewer is supposed to happen over GitLab as well, e.g., by opening merge requests and issues.
Contents
In this NOWA workshop on GitLab CI & Code Review you will learn…
… what CI is and what it does
… how to set it up on GitLab
… which pipelines there are and how to use them for your own project
… what a code review process involves on both the developer as well as the reviewer site
Preparations
For this workshop you have to know the basics in Git and GitLab. For this, you can go through this workshop prior to this workshop.
Furthermore, you need to know how to write tests for your code. For this, you can go through our previous code workshop and/or this code handbook.
Materials
- Presentation slides are available here.
- Example GitLab repos used in this workshop for you to fork: MatlabCI, PythonCI