Conan 1 packages in the package registry

Publish Conan packages in your project’s package registry. Then install the packages whenever you need to use them as a dependency.

To publish Conan packages to the package registry, add the package registry as a remote and authenticate with it.

Then you can run conan commands and publish your package to the package registry.

For documentation of the specific API endpoints that the Conan package manager client uses, see Conan v1 API or Conan v2 API.

Learn how to build a Conan 1 package.

Add the package registry as a Conan remote

To run conan commands, you must add the package registry as a Conan remote for your project or instance. Then you can publish packages to and install packages from the package registry.

Add a remote for your project

Set a remote so you can work with packages in a project without having to specify the remote name in every command.

When you set a remote for a project, there are no restrictions to your package names. However, your commands must include the full recipe, including the user and channel, for example, package_name/version@user/channel.

To add the remote:

1. In your terminal, run this command:

   conan remote add gitlab https://gitlab.example.com/api/v4/projects/<project_id>/packages/conan

2. Use the remote by adding --remote=gitlab to the end of your Conan command.

   For example:

   conan search Hello* --remote=gitlab

Add a remote for your instance

Use a single remote to access packages across your entire GitLab instance.

However, when using this remote, you must follow these package naming restrictions.

To add the remote:

1. In your terminal, run this command:

   conan remote add gitlab https://gitlab.example.com/api/v4/packages/conan

2. Use the remote by adding --remote=gitlab to the end of your Conan command.

   For example:

   conan search 'Hello*' --remote=gitlab

Package recipe naming convention for instance remotes

The standard Conan recipe convention is package_name/version@user/channel, but if you’re using an instance remote, the recipe user must be the plus sign (+) separated project path.

Example recipe names:

Project remotes have a more flexible naming convention.

Authenticate to the package registry

GitLab requires authentication to upload packages, and to install packages from private and internal projects. (You can, however, install packages from public projects without authentication.)

To authenticate to the package registry, you need one of the following:

• A personal access token with the scope set to api.
• A deploy token with the scope set to read_package_registry, write_package_registry, or both.
• A CI job token.

Add your credentials to the GitLab remote

Associate your token with the GitLab remote, so that you don’t have to explicitly add a token to every Conan command.

Prerequisites:

• You must have an authentication token.
• The Conan remote must be configured.

In a terminal, run this command. In this example, the remote name is gitlab. Use the name of your remote.

conan user <gitlab_username or deploy_token_username> -r gitlab -p <personal_access_token or deploy_token>

Now when you run commands with --remote=gitlab, your username and password are included in the requests.

Set a default remote for your project (optional)

If you want to interact with the GitLab package registry without having to specify a remote, you can tell Conan to always use the package registry for your packages.

In a terminal, run this command:

conan remote add_ref Hello/0.1@mycompany/beta gitlab

If you don’t set a default user or remote, you can still include the user and remote in your commands:

CONAN_LOGIN_USERNAME=<gitlab_username or deploy_token_username> CONAN_PASSWORD=<personal_access_token or deploy_token> <conan command> --remote=gitlab

Publish a Conan package

Publish a Conan package to the package registry, so that anyone who can access the project can use the package as a dependency.

Prerequisites:

• The Conan remote must be configured.
• Authentication with the package registry must be configured.
• A local Conan package must exist.
  • For an instance remote, the package must meet the naming convention.
• You must have the project ID, which is displayed on the project overview page.

To publish the package, use the conan upload command:

conan upload Hello/0.1@mycompany/beta --all

Publish a Conan package by using CI/CD

To work with Conan commands in GitLab CI/CD, you can use CI_JOB_TOKEN in place of the personal access token in your commands.

You can provide the CONAN_LOGIN_USERNAME and CONAN_PASSWORD with each Conan command in your .gitlab-ci.yml file. For example:

create_package:
  image: conanio/gcc7
  stage: deploy
  script:
    - conan remote add gitlab ${CI_API_V4_URL}/projects/$CI_PROJECT_ID/packages/conan
    - conan new <package-name>/0.1 -t
    - conan create . <group-name>+<project-name>/stable
    - CONAN_LOGIN_USERNAME=ci_user CONAN_PASSWORD=${CI_JOB_TOKEN} conan upload <package-name>/0.1@<group-name>+<project-name>/stable --all --remote=gitlab
  environment: production

Additional Conan images to use as the basis of your CI file are available in the Conan docs.

Re-publishing a package with the same recipe

When you publish a package that has the same recipe (package-name/version@user/channel) as an existing package, the duplicate files are uploaded successfully and are accessible through the UI. However, when the package is installed, only the most recently-published package is returned.

Install a Conan package

Install a Conan package from the package registry so you can use it as a dependency. You can install a package from the scope of your instance or your project. If multiple packages have the same recipe, when you install a package, the most recently-published package is retrieved.

Conan packages are often installed as dependencies by using the conanfile.txt file.

Prerequisites:

• The Conan remote must be configured.
• For private and internal projects, you must configure Authentication with the package registry.

1. In the project where you want to install the package as a dependency, open conanfile.txt. Or, in the root of your project, create a file called conanfile.txt.

2. Add the Conan recipe to the [requires] section of the file:

   [requires]
   Hello/0.1@mycompany/beta
   
   [generators]
   cmake

3. At the root of your project, create a build directory and change to that directory:

   mkdir build && cd build

4. Install the dependencies listed in conanfile.txt:

   conan install .. <options>

Remove a Conan package

There are two ways to remove a Conan package from the GitLab package registry.

• From the command line, using the Conan client:

  conan remove Hello/0.2@user/channel --remote=gitlab

  You must explicitly include the remote in this command, otherwise the package is removed only from your local system cache.

  This command removes all recipe and binary package files from the package registry.

• From the GitLab user interface:

  Go to your project’s Deploy > Package registry. Remove the package by selecting Remove repository ( ).

Search for Conan packages in the package registry

To search by full or partial package name, or by exact recipe, run the conan search command.

• To search for all packages with a specific package name:

  conan search Hello --remote=gitlab

• To search for a partial name, like all packages starting with He:

  conan search He* --remote=gitlab

The scope of your search depends on your Conan remote configuration:

• If you have a remote configured for your instance, your search includes all projects you have permission to access. This includes your private projects as well as all public projects.

• If you have a remote configured for a project, your search includes all packages in the target project, as long as you have permission to access it.

Fetch Conan package information from the package registry

The conan info command returns information about a package:

conan info Hello/0.1@mycompany/beta

Download a Conan package

You can download a Conan package’s recipe and binaries to your local cache without using settings that use the conan download command.

Prerequisites:

• The Conan remote must be configured.
• For private and internal projects, you must configure authentication with the package registry.

Download all binary packages

You can download all binary packages associated with a recipe from the package registry.

To download all binary packages, run the following command:

conan download Hello/0.1@foo+bar/stable --remote=gitlab

Download recipe files

You can download only the recipe files without any binary packages.

To download recipe files, run the following command:

conan download Hello/0.1@foo+bar/stable --remote=gitlab --recipe

Download a specific binary package

You can download a single binary package by referencing its package reference (known as the package_id in Conan documentation).

To download a specific binary package, run the following command:

conan download Hello/0.1@foo+bar/stable:<package_reference> --remote=gitlab

Supported CLI commands

The GitLab Conan repository supports the following Conan CLI commands:

• conan upload: Upload your recipe and package files to the package registry.
• conan install: Install a Conan package from the package registry, which includes using the conanfile.txt file.
• conan download: Download package recipes and binaries to your local cache without using settings.
• conan search: Search the package registry for public packages, and private packages you have permission to view.
• conan info: View the information on a given package from the package registry.
• conan remove: Delete the package from the package registry.

Extract Conan metadata

When you upload a Conan package, GitLab automatically extracts metadata from the conaninfo.txt file. This metadata includes:

• Package settings (like os, arch, compiler and build_type)
• Package options
• Package requirements and dependencies

Conan revisions

Conan 1 revisions provide package immutability in the package registry. When you make changes to a recipe or a package without changing its version, Conan calculates a unique identifier (revision) to track these changes.

Types of revisions

Conan uses two types of revisions:

• Recipe revisions (RREV): Generated when a recipe is exported. By default, Conan calculates recipe revisions using the checksum hash of the recipe manifest.
• Package revisions (PREV): Generated when a package is built. Conan calculates package revisions using the hash of the package contents.

Enable revisions

Revisions are not enabled by default in Conan 1.x. To enable revisions, you must either:

• Add revisions_enabled=1 in the [general] section of your _conan.conf_ file (preferred).
• Set the CONAN_REVISIONS_ENABLED=1 environment variable.

Reference revisions

You can reference packages in the following formats:

Upload revisions

To upload all revisions and their binaries to the GitLab package registry:

conan upload package_name/version@user/channel#* --all --remote=gitlab

When you upload multiple revisions, they are uploaded from oldest to newest. The relative order is preserved in the registry.

Search for revisions

To search for all revisions of a specific recipe in Conan v1:

conan search package_name/version@user/channel --revisions --remote=gitlab

This command displays all available revisions for the specified recipe along with their revision hashes and creation dates.

To get detailed information about a specific revision:

conan search package_name/version@user/channel#revision_hash --remote=gitlab

This command shows you the specific binary packages available for that revision.

Delete packages with revisions

You can delete packages at different levels of granularity:

Delete a specific recipe revision

To delete a specific recipe revision and all its associated binary packages:

conan remove package_name/version@user/channel#revision_hash --remote=gitlab

Delete packages for a specific recipe revision

To delete all packages associated with a specific recipe revision:

conan remove package_name/version@user/channel#revision_hash --packages --remote=gitlab

Delete a specific package in a revision

To delete a specific package in a recipe revision, you can use either of these commands:

conan remove package_name/version@user/channel#revision_hash -p package_id --remote=gitlab

Or:

conan remove package_name/version@user/channel#revision_hash:package_id --remote=gitlab

Immutable revisions workflow

Revisions are designed to be immutable. When you modify a recipe or its source code:

• A new recipe revision is created when you export a recipe.
• Any existing binaries that belong to the previous recipe revision are not included. You must build new binaries for the new recipe revision.
• When you install a package, Conan automatically retrieves the latest revision unless you specify a revision.

For package binaries, you should include only one package revision per recipe revision and package reference (known as the package_id in Conan documentation). Multiple package revisions for the same recipe revision and package ID indicate that a package was rebuilt unnecessarily.

Troubleshooting

Make output verbose

For more verbose output when troubleshooting a Conan issue:

export CONAN_TRACE_FILE=/tmp/conan_trace.log # Or SET in windows
conan <command>

You can find more logging tips in the Conan documentation.

SSL Errors

If you are using a self-signed certificate, there are two methods to manage SSL errors with Conan:

• Use the conan remote command to disable the SSL verification.
• Append your server crt file to the cacert.pem file.

Read more about this in the Conan Documentation.