diff --git a/extensions/commands/art/README.md b/extensions/commands/art/README.md index 5e162e4..6c2969d 100644 --- a/extensions/commands/art/README.md +++ b/extensions/commands/art/README.md @@ -43,6 +43,8 @@ conan create . --format json -s build_type=Release > create_release.json conan create . --format json -s build_type=Debug > create_debug.json ``` +**Note**: In case you are using different machines or different Conan cache folders (e.g. when running on a CI system), the recommended flow is to previously upload the recipe to Artifactory and then use ``conan install --requires= --build= `` + ``conan test ...`` on each machine to create the binaries for different configurations. This is the way to make sure you operate over the same recipe revision and its metadata files across all the CI machine agents. + Then upload the created package to your repository: ``` @@ -63,7 +65,7 @@ conan art:build-info create create_debug.json mybuildname_debug 1 --server my_artifactory --with-dependencies > mybuildname_release.json ``` -### 3. Upload the build infos to your Artifactory server +#### 3. Upload the build infos to your Artifactory server Finally, you can upload the Build Info's: @@ -72,25 +74,25 @@ conan art:build-info upload mybuildname_release.json --server my_artifactory conan art:build-info upload mybuildname_debug.json --server my_artifactory ``` -### 4. Aggregate build infos into one +#### 4. Aggregate build infos into one In this case we generated two Build Info's, for Release and Debug, but we can also merge those to create a new Build Info that aggregates that information: ``` conan art:build-info append mybuildname_aggregated 1 --build-info=mybuildname_release,1 --build-info=mybuildname_debug,1 --server my_artifactory > mybuildname_aggregated.json -conan art:build-info upload mybuildname_aggregated.json --server my_artifactory" +conan art:build-info upload mybuildname_aggregated.json --server my_artifactory ``` This is handy in order to make promotions of packages from one repository to another in Artifactory. -### 5. Promote all the binaries of the aggregated build info +#### 5. Promote all the binaries of the aggregated build info ``` -conan art:build-info promote mybuildname_aggregated 1 origin-artifactory-repo destination-artifactory-repo --server my_artifactory} +conan art:build-info promote mybuildname_aggregated 1 origin-artifactory-repo destination-artifactory-repo --server my_artifactory ``` -Now, both release and debug binaries from that pacakge ae available in the destination repository with just one command. +Now, both release and debug binaries from that package are available in the destination repository with just one command. #### [conan art:promote](cmd_promote.py)