From 9e1d6d7a51f1a80033e83dbf1d65abbe76e6a209 Mon Sep 17 00:00:00 2001 From: Olivier Filangi Date: Mon, 25 Sep 2023 10:44:47 +0200 Subject: [PATCH] Update README.md --- profile/ci_cd_best_practices/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/profile/ci_cd_best_practices/README.md b/profile/ci_cd_best_practices/README.md index 65600ed..522b6fd 100644 --- a/profile/ci_cd_best_practices/README.md +++ b/profile/ci_cd_best_practices/README.md @@ -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.