Make all jobs report artifacts use source relative paths.

Created on 3 May 2024, 12 months ago

GitLab expects all report paths to be relative to the build, how very many of our reports include the full path

For example:

Fillename: /builds/project/keycdn/tests/src/FunctionalJavascript/ExampleTest.php

Clicking on the path returns:

"...keycdn/tests/src/FunctionalJavascript/ExampleTest.php" did not exist on "01b04a7a410c2eeed34d2a5495cf73ea8d6ba8b4"

The incorrect base path makes it harder/slower to review code.

Cause each test that generates assets to generate a report.

Ensure all report paths are relative to the source root.

Determine which tests generate reports that are not relative
to the source root.
Modify each test to cleanup the assets.

🐛 Bug report

Status

Active

Component

gitlab-ci

Created by

🇺🇸United States cmlara

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @cmlara
Comment 6 months ago →
🇬🇧United Kingdom jonathan1055
This issue for PHPUnit is trying to solve a similar thing I think -
✨ Add basepath parameter to PHP Code Sniffer Active
Comment 6 months ago →
🇩🇪Germany simonbaese Berlin
This issue might also be related 📌 Tweak PHPStan config so paths are always correct and baseline is more usable Active .
Comment 6 months ago →
🇬🇧United Kingdom jonathan1055
Yes, absolutely. That issue was already referencing this one.
Comment 2 months ago →
🇬🇧United Kingdom jonathan1055
Added cspell issue 📌 CSPELL is checking recipes/readme.txt - change to run in project folder Active
Comment 2 months ago →
🇬🇧United Kingdom jonathan1055
CSpell issue was unrelated, the artifacts are fine, as they do not contain any paths.

Production build 0.71.5 2024