Revert delete prefix for junit attachment path
Ref: #330955 (closed)
What does this MR do?
This MR reverts !62520 (merged) which was an attempt to move our business logic to strip out the build group project path from our capybara configuration to our junit parser.
Why are we doing this?
We are not able to read $CI_PROJECT_DIR from the job itself during our junit parsing.
After checking this on production, it turns out that this does not work as expected, as you can see on this failed pipeline.
The path is not correct and the screenshot links to a 404 for the test suite rspec-ee system pg12.
Let's change it back to modify the path with our capybara configuration.
Does this MR meet the acceptance criteria?
Conformity
- [-] I have included a changelog entry, or it's not needed. (Does this MR need a changelog?)
- [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
- [-] I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
- [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
- [-] I have self-reviewed this MR per code review guidelines.
-
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) - [-] I have tested this MR in all supported browsers, or it's not needed.
- [-] I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team