Skip to content

Add note about CI flow to the build info readme #222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
czoido merged 2 commits into from
Nov 25, 2025
Merged

Add note about CI flow to the build info readme #222

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
88ca0c4
Add note about CI flow to the build info readme
danimtb Nov 25, 2025
e2aa9e0
Update extensions/commands/art/README.md
danimtb Nov 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions extensions/commands/art/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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=<pkg> --build=<pkg> `` + ``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:

```
Expand All @@ -63,7 +65,7 @@ conan art:build-info create create_debug.json mybuildname_debug 1 <artifactory-r
conan art:build-info create create_release.json mybuildname_release 1 <artifactory-repo1> <artifactory-repo2> --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:

Expand All @@ -72,25 +74,25 @@ conan art:build-info upload mybuildname_release.json --server my_artifactory
conan art:build-info upload mybuildname_debug.json <url> --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)

Expand Down
Loading