Add Release Evidence detail to the chain of custody export
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to Solve
Compliance-minded organizations rely on evidence artifacts to pass their internal or external audits. A significant piece of evidence is the chain of custody for their software release process. In #213364 (closed) we will introduce an MVC to export all of the commits for a project in a given date range, but that lacks the level of detail for our customers who need to see the larger picture of a release.
Intended users
- Sidney (Systems Administrator)
- The management stakeholders who adhere to any auditing process. To be defined in a new Compliance Persona
Proposal
Iterate on the existing export to add additional detail from the Category:Release Evidence artifact:
| Commit | Author | Merge Request | Merged By | Source Branch | Target Branch | Group | Project | Approver(s) | Milestone(s) | Release | Pipeline | Released At |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SHA | Jeremy | !439858 | Matt | my-feature-branch | master | My-Group | awesome-project | Daffy Duck | v4.0-rc1 | April Release | pipeline_id | 2020-04-01 13:23:40 UTC |
| SHA | Jeremy | None | Jeremy | None | master | My-Group | awesome-project | None | v4.0-rc1 | April Release | pipeline_id | 2020-04-01 13:23:40 UTC |
Permissions and Security
This would be accessible only to Group Owners and Admins
Documentation
Availability & Testing
What does success look like, and how can we measure that?
- Number of times this report is exported
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by 🤖 GitLab Bot 🤖