Package: Enable teams by automatically testing Images and confirming they can be built

Problem to solve

When looking at the package or container registries, it is very difficult to understand the viability of that artifact. Users would like a way to know in the UI if the package can be built, has passed a series of tests, or even if an individual approved the package/image for use.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)

Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->

Further details

The rules required to append the verified UI moment to individual packages or images varies depending on the situation.

• all that is needed is "Can the image be built into a container" or "does this package successfully complete a build without errors".
• Append the verified UI moment to a package or image if it successfully passed a series of tests.
• Append the verified UI moment only after a maintainer-level user manually approves the package (and it passes tests).

Proposal

As an MVC, I propose we add a ✅ in the Registry UI to confirm the image or package can be successfully run in a dummy environment. If it fails, we may add a ⚠ type indicates that the image/package is non-functional.

Permissions and Security

As we introduce more complex verifications

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references