WIP: Static code analysis on xls branch

Validate:

• Pass all the tests
• Don't left dangling images
• The CI's test stage can use all the containers
• Check containers with Tenable

added 1 commit

• 0d8c50fb - fix tags

Compare with previous version

added 1 commit

• da90092f - style: fix typo

Compare with previous version

marked the checklist item Pass all the tests as completed

marked the checklist item Don't left dangling images as completed

unmarked as a Work In Progress

changed the description

added 1 commit

• 2142eb9d - chore: run unl-its/static-code-analysis container

Compare with previous version

added 1 commit

• 612f856f - fix: typo

Compare with previous version

marked as a Work In Progress

changed the description

changed target branch from master to working-copy

@s-anelso56, maybe we must define for each container how we will test if have the required tools or not, and if they work as expected. For instance, we can test the container unl-its/php-lint:7.0 validating if the PHP version match with 7.0:

docker run --rm unl-its/php-lint:7.0 php -v | egrep -q "^PHP 7\.0\..* "

(We can add a -q to egrep to use just the exit code.)

We could use the docker.cmd LABEL to describe how to use the container and create the tests based on this label.

added 1 commit

• bb43e750 - add Tenable support

Compare with previous version

added 1 commit

• 3ab0e1ec - fix: hide tokens in the logs

Compare with previous version

added 1 commit

• 66857434 - chore: re-enable gitlab-ci jobs

Compare with previous version

added 2 commits

• 1aaf885d - fix: Makefile linter problem
• 5278cfd5 - Merge branch 'static-code-analysis-on-xls-branch' of…

Compare with previous version

changed the description

added 1 commit

• 0f8d2665 - add nodejs and nmp support to static-code-analysis

Compare with previous version

closed