Exposing Relevant Artifacts for Non-SLC-Generating EDP Projects

[angelmp01]

Problem

The EDP-generated System Life Cycle (SLC) documentation depends on artifacts created during the technical delivery process, such as test execution results and installation logs. However, if an EDP project does not generate SLC documentation (e.g., due to the System Owner opting for an alternative approach), these critical artifacts remain inaccessible within the EDP's Release Manager. This creates a gap in supporting the chosen approach for documentation.

Solution

To address this issue, the EDP will ensure that relevant artifacts are exposed even when SLC documentation is not generated. Specifically:

For each Release Manager run (irrespective of whether EDP documents are generated), a dedicated Nexus folder will be created.
This folder will contain:

• A combined test execution report document (xUnit XML).
• Per-component installation logs.

The Nexus folder will be accessible to all EDP project roles.
An EDP Onboarding article will provide guidance on how to download the full Nexus folder.

This solution ensures that all necessary artifacts are available to support alternative documentation approaches.

Describe alternatives you've considered

Maintain the evidences in the Jenkins workspace with a dedicated PVC to store this evidences (is not needed to store all the workspace)