Conan is a C/C++ Package Manager. The Artifactory Pipeline DSL includes APIs that make it easy for you to run Conan builds, using the Conan Client installed on your build agents. Here's what you need to do before you create your first Conan build job with Jenkins:
1, Install the latest Conan Client on your Jenkins build agent. Refer to the Conan documentation for installation instructions.
2. Add the Conan Client executable to the PATH environment variable on your build agent, to make sure Jenkins is able to use the client.
3. Create a Conan repository in Artifactory as described in the Conan Repositories Artifactory documentation.
OK. Let's start coding your first Conan Pipeline script.
We'll start by creating an Artifactory server instance, as described at the beginning of this article.
Here's an example:
def server = Artifactory.server 'my-server-id'
Now let's create a Conan Client instance
def conanClient = Artifactory.newConanClient()
When creating the Conan client, you can also specify the Conan user home directory as shown below:
def conanClient = Artifactory.newConanClient userHome: "conan/my-conan-user-home"
We can now configure our new conanClient instance by adding an Artifactory repository to it. In our example, we're adding the 'conan-local' repository, located in the Artifactory server, referenced by the server instance we obtained:
String remoteName = conanClient.remote.add server: server, repo: "conan-local" |
The above method also accepts the the following optional arguments:
force: true - Adding this argument will make the conan client not to raise an error. If an existing remote exists with the provided name.
verifySSL: false - Adding this argument will make the conan client skip the validation of SSL certificates.
As you can see in the above example, the conanClient.remote.add method returns a string variable - remoteName. What is this 'remoteName' variable? What is it for?
Well, a 'Conan remote' is a repository, which can be used to download dependencies from and upload artifacts to. When we added the 'conan-local' Artifactory repository to our Conan Client, we actually added a Conan remote. The 'remoteName' variable contains the name of the new Conan remote we added.
OK. We're ready to start running Conan commands. You'll need to be familiar with the Conan commands syntax, exposed by the Conan Client to run the commands. You can read about the commands syntax in the Conan documentation.
Let's run the first command:
def buildInfo1 = conanClient.run command: "install --build missing" |
The 'conanClient.run' method returns a buildInfo instance, that we can later publish to Artifactory. If you already have a buildInfo instance, and you'd like the 'conanClient.run' method to aggregate the build-info to it, you can also send the buildInfo instance to the run command as and an argument as shown below:
conanClient.run command: "install --build missing", buildInfo: buildInfo |
The next thing we want to do is to use the Conan remote we created. For example, let's upload our artifacts to the Conan remote. Notice how we use the 'remoteName' variable we got earlier, when building the Conan command:
String command = "upload * --all -r ${remoteName} --confirm"
conanClient.run command: command, buildInfo: buildInfo |
We can now publish the the buildInfo to Artifactory, as described in the Publishing Build-Info to Artifactory section. For example:
server.publishBuildInfo buildInfo |