Improve pipeline debugging by displaying failure information with packages

Background

This issue relates to the UX scorecard recommendations issue

Problem

A user investigating a failed pipeline needs to do manual work to find out which package was involved in the failure.

When I'm debugging a failed job by investigating a package dependency in the package registry, it's hard for me to understand which package was involved in the pipeline failure. In order to figure it out, I need to remember the name and version of the package involved in the failure and find it in the list.

Reasons it may be hard to find a certain package from the package list:

• The package list is sorted most recently published -> least recently published by default. This does not mean that the package my project uses will necessarily be the top of the list
• The package list shows all versions of a package
• The package list may contain packages that are not relevant to me (related: package clean up issue: #227233 (closed))

Current workflow

Reference the name and version of the package from the job log and code and scan and/or filter the list by these attributes

Questions

• What information would make sense to show? Keeping in mind multiple people collaborating on a project.
• Is it technically possible to surface this information?
• How would this work on for package registry that is used for multiple projects?

Potential solutions

• Sort package list by recently consumed
• Indicate on the table of packages that there was a pipeline failure that links to the pipeline