By understanding its syntax, options, and the critical concept of remote priority, you can design robust, efficient dependency workflows—from a single developer’s laptop to a large-scale enterprise CI/CD pipeline. Always remember: remotes give you control over where your binaries come from, and conan add remote is the key.
conan remote remove <remote-name>
conan add remote [name] [url] [verify_ssl]
: A unique alphanumeric name you choose to identify the repository locally. url : The full network address of the Conan repository API. conan add remote
Instead of conan add remote , you can define remotes via environment variables for CI/CD pipelines:
: Don't just name a remote "test." Use names like prod-binary-cache or team-alpha-dev .
: Use the -f or --force flag to overwrite an existing remote with the same name. By understanding its syntax, options, and the critical
The conan remote add command is the gateway to linking your local Conan client to these external package registries. Understanding Conan Remotes
Let's walk through a practical CI/CD scenario where conan add remote is indispensable.
: The exact repository API endpoint provided by your hosting platform. url : The full network address of the Conan repository API
: Allows you to specify the position in the remote list (default is at the end).
export CONAN_LOGIN_USERNAME_<REMOTE>=<username> export CONAN_PASSWORD_<REMOTE>=<password>
conan user -p <YOUR_API_KEY> -r artifactory <YOUR_EMAIL>