continuous integration (CI) support for on-premise/self-hosted gitlab

[imme-emosol]

Gitlab CI support

As I have some experience with gitlab-ci , I felt a need to respond to some of the things mentioned in #8256 .

---

Code Quality

Redirecting phpstan its output to a file (generating a report)

We don't know the filename to write.

Not knowing the filename seems to be less of a concern, given that phpstan its output can be redirected to a file.

The second run should only take a fraction of the time thanks to phpstans result cache, as long as they are run in the same container
From a comment in issue 8256.

It might be good to mention that running phpstan multiple times in the same environment should have little time-impact and that it can therefore be used to generate several outputs.

---

CodeClimate / AutoDevOps

Looks like there's something called CodeClimate and it has plugins which are supported by GitLab somehow automatically, but I haven't looked too much into it: https://docs.codeclimate.com/docs/list-of-engines

Gitlab runs CodeClimate when manually set up to do so, or when AutoDevOps is enabled.

CodeClimate plugins

I think it's not a stretch that PHPStan could be among these plugins as well, but I don't know what it entails.

What adding PHPStan to CodeClimate entails might be determined by looking at other plugins. For instance:

• Runner.php for PHP Mess Detector
• Runner.php for PHP Code Sniffer

NOTE! - CodeClimate is on infrastructure of someone else

At this moment, using CodeClimate/AutoDevOps seems to not be an option for code that cannot leave a (private) network.

---

Code(/Type) Coverage

The code quality visualization availability in the Gitlab 'Free' Tier is limited compared to other tiers. Another metric that could be somewhat useful, is the percentage covered by phpstan, 'type coverage'. This can be done by adding coverage to gitlab-ci.yml with a regular expression that is matched against the, i assume stdout only, output produced by the ci-job (coverage: regex examples).

---

Suggestion for CI Page

A suggestion to create a page dedicated to pointing to suggestion for CI (an index of pointers).

Such a page could mention these pages:

• supported output formats, supported auto-detection (w/ table) : https://phpstan.org/user-guide/output-format
• suggestion for the naming of phpstan its configuration file : https://phpstan.org/config-reference#config-file
• for customizing output for unsupported ci : https://phpstan.org/developing-extensions/error-formatters#special-format-for-continuous-integration-(ci)

---