GitLab¶

https://status.management.confirm.ch/api/badge/25/status?style=flat-square

We make extensive use of GitLab, by using it for the following topics:

Use it as a Git collaboration platform
To do our ScrumC sprint planning
To run our GitLab CI pipelines
To support our DevOps culture

Hint

GitLab is automatically deployed via CI/CD pipelines in the GitLab project – it basically deploys “itself”.

GitLab Flavored Markdown¶

As mentioned in the documentation chapter, we’re documenting most of our projects directly in Markdown files (e.g. README.md) in GitLab.

While GitLab supports the basic Markdown syntax, it also supports the enhanced GitLab Flavored Markdown (GLFM) version.

Hint

Nice to know are the following enhancements:

GitLab-specific references
Diagrams and flowcharts (we’re using our own PlantUML)
Table of contents
Alerts
Collapsible section

GitLab Guard¶

GitLab Guard was born out of the chaos during the early days of our «GitLab journey», when we dove head first into using GitLab & GitLab CI for our «Infrastructure as Code» setup.

It’s the guardian for all GitLab projects, which validates & enforces GitLab project settings.

Hint

In our infrastructure, GitLab is automatically run in the CI/CD pipeline of the GitLab Guard infrastructure project. However, GitLab Guard itself is developed, and maintained in the GitLab Guard product project.