Display more robust historical data of the package on the package detail view
Problem to solve
The Package stage allows you to publish, consume and discover packages, all in one place. Users publish and pull packages using GitLab CI/CD, the command line or the GitLab API.
When a user needs to troubleshoot a problem related to a package, they are lacking in relevant data on the package UI, requiring workarounds like using the commit sha as the reference throughout the process. They are also looking for information on what has changed in this particular version of the package.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Further details
Proposal
On the package detail screen, we add an additional "Activity" section that lays out the activities the package has gone through to get to the registry, including:
- The commit data that triggered the build of the package (with an expandable option displaying the commit message, often used to help users understand what's happened in the
- The pipeline the package was built from (in CI)
- The date and time the package was published to the registry.
Permissions and Security
n/a
Documentation
- Screenshots of the package detail screen should be updated to include the activity section.
- Documentation should be added to explain what the different possible activities seen on this UI.
Availability & Testing
n/a
What does success look like, and how can we measure that?
Implementing the new UI inclusive with relevant data will enable our users to troubleshoot issues related to packages.
