docs(CI): answer question 1.4
Refs: #4 Signed-off-by: Klagarge <remi@heredero.ch>
This commit is contained in:
@@ -14,4 +14,7 @@
|
|||||||
|
|
||||||
## Q1.3
|
## Q1.3
|
||||||
- A linter is a tool to statically analyse code for readability and improving code quality. It is usually executed from a standalone tool.
|
- A linter is a tool to statically analyse code for readability and improving code quality. It is usually executed from a standalone tool.
|
||||||
- It is used to check for errors, vulns, code smells or general issues but also to enforce a coding style over the whole project.
|
- It is used to check for errors, vulns, code smells or general issues but also to enforce a coding style over the whole project.
|
||||||
|
|
||||||
|
## Q1.4
|
||||||
|
The minimum is to change the image on the CI to put an Alpine or a basic python image. Another option (which we implemented) is to create a custom Docker image that includes all the necessary dependencies for the application. This can significantly reduce the time required to set up the environment and speed up the CI/CD pipeline.
|
||||||
|
Reference in New Issue
Block a user