Display full Conan recipe on packages list page

Problem to solve

The GitLab Conan Repository allows you to build, publish, and share your C/C++ dependencies alongside your source code and pipelines. However, when using the Package Registry user interface to find and/or verify a dependency, it can be difficult to differentiate between different versions of a given dependency.

The issue is that the user interface currently presents the package name and version and does not include conan_user and conan_channel. Both of which are often used as identifiers between two different packages. For example, the below example would all be displayed in the UI as Hello version 1.0.

Hello/1.0@sabrams/stable
Hello/1.0@sabrams/beta
Hello/1.0@other_user/stable

Screen_Shot_2020-08-20_at_2.55.51_PM

Intended users

User experience goal

  • A user can easily distinguish between different versions of their Conan package.

Proposal

Display the full recipe for Conan packages on the packages (/-/packages) list page.

Screen_Shot_2020-09-08_at_13.16.11

The Package detail should be updated in a similar way:

Screen_Shot_2020-09-08_at_13.18.58

The "Other versions" tab will be updated to show when the versions are the same but the channels are different. For example, all three of the examples should be shown in the Other versions tab.

Hello/1.0@sabrams/beta
Hello/1.0@sabrams/stable
Hello/2.0@sabrams/stable

Further details

Beyond this issue

We will want to think about how to display the different "configurations" as seen in the conan-center packages. An audit of expected package metadata is being done in issue: https://gitlab.com/gitlab-org/ci-cd/package-stage/package/-/issues/3#note_395751854

Screen_Shot_2020-09-10_at_2.16.41_PM

Permissions and Security

  • There are no expected permissions changes for this issue

Documentation

  • There are no expected documentation changes for this issue

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

This issue is part of an on-going effort to drive adoption and usage of the Conan Repository. We will measure success by measuring how many Conan packages are published/installed per day and the number of page views to /packages.

Links / references

Edited by Tim Rizzi