TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Package Management

2 posts · Mar 2020 – Sep 2020

What this trail covers

GitLab introduced a repository for composer packages in version 13.3, allowing users to store and manage private and public composer packages within their GitLab instance. This feature enables the creation of packages via `.gitlab-ci.yml` templates, automatically generating packages when Git tags are created or commits are pushed to branches. Migration of existing packages is supported via manual `curl` commands or a community-provided script. Future improvements include enhanced GUI details on packages and support for Conan packages. This post details the integration of Conan, a C/C++ package manager, allowing users to set GitLab as a remote registry for their packages, enabling them to upload and install packages directly from GitLab's registry. This allows for code and generated packages to live in the same place, simplifying management and enabling automatic building and consumption of packages via CI pipelines. Future iterations will include a UI for Conan packages and project/group level support.

All GitLab trails
  1. Migrate composer packages to GitLabThis post details the introduction of a Composer package repository in GitLab 13.3, enabling users to store and manage private and public Composer packages. It outlines how to create packages using `.gitlab-ci.yml` templates and provides two methods for migrating existing packages: manual `curl` requests to the GitLab API and a community script. The post also highlights current limitations and areas for improvement, such as GUI details on package size and publication, and full semantic versioning support, linking to relevant GitLab issues.
  2. Modern C and C++: How Conan integration works in GitLabThis post introduces the integration of Conan, a C/C++ package manager, with GitLab's package registry. It explains how users can configure GitLab as a remote registry for Conan, enabling them to upload and download packages. The post highlights the benefits of having code and generated packages co-located within GitLab, simplifying workflows and enabling automated CI/CD pipelines for package building and consumption. It also outlines future plans for Conan integration, including a UI for package metadata and project/group level support.