W8: As developers we want to enhance our CI pipelines with at least three static analysis tools

[OLaursen]

In our repository we must add:

• One linter for our main programming language (C#)
• One code formatter for our main programmaing language(C#)
• One linter for our Dockerfiles
• Other suitable linters we might find appropiate, such as for shell scripts(shellcheck).

We need to add these analysis tools as a software quality gate in our CI/CD pipelines.

AC:

• When a threshold is defined for how high our code quality should be, to avoid aborting delivery and deployment. OR that we in case of failure trust that the tool can automatically correct the code.
• When linters and formatters are added to the repositories.

[casperh123]

We have a Formatter and Linter for C#, that automatically lints and formats pushes. The Linter CodeAC also includes linting for Docker, even though this is not a seperate linter. For static analysis we now have:

• Cshariper for C# linting and formatting.
• Sonarcloud for static code analysis.
• CodeAC for C# and dockerfile code analysis.