This is the next stage of
request #13038.
Goal here is to be able to integrate and enforce Psalm checks in our test pipeline.
Due to the resources needed to achieve the static analysis, we might be forced to only check modified files of each patchset which means we might miss changes affecting the unmodified parts of the codebase.
This request will mostly be about the stabilization of what we already have, most issues/false positives are due to the way(s) Tuleap loads its classes and files, depending on the entry point you might encounter functions/classes that are not loaded but exist in the codebase. This does not help tools analyzing code at all.
This request will also take care of solving issues spotted by Psalm introduced since we run Psalm in the nightly pipeline.
We will also need to wait for the next release of Psalm (current release 3.2.9) to not have to work around some issues (e.g. [0])
[0]
https://github.com/vimeo/psalm/issues/1542