Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions profile/ci_cd_best_practices/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ CI/CD should be used to:
- get a **test-coverage report** (optional - best practice)
- **analyze your code** using a specific tool (*e.g.*: [sonarqube](https://sonarsource.com/)) and detect potential security issues, bugs, bad practices, ... (if applicable - highly recommended)
- generate **archives** from a functional code / releases and host them on GitLab using **artifacts** and/or **package** mechanisms (optional)
- automating the process of deploying software versions and execution environments to centralized repositories such as Docker Hub, NPM, Maven, and others.

> Note: for artifacts, we recommend you to keep releases artifacts without time restriction.
> Artifacts generated by **dev branches** should be **kept 24h** or 1 week.
Expand Down