Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
46 changes: 46 additions & 0 deletions docs/user/how-to/build-component.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ Built packages are placed in structured subdirectories under the project's outpu
| `--srpm-only` | Build only the SRPM, not the binary RPMs |
| `--preserve-buildenv on-failure` | Keep the mock chroot on build failure for debugging |
| `--continue-on-error` / `-k` | Continue building remaining components if one fails |
| `--unique-mockroot` | Use distinct mock roots instead of the shared default root |
| `--local-repo <path>` | Add a local RPM repository for build dependencies |
| `--local-repo-with-publish <path>` | Use a local repo and publish built RPMs into it |

Expand All @@ -49,6 +50,51 @@ azldev comp build --local-repo-with-publish ./base/out -p dep-package -p main-pa
2. Enter the chroot with `azldev adv mock shell` to inspect the build environment
3. Check build logs in the project's log directory

## Isolate Mock Roots

Use the global `--unique-mockroot` flag to avoid sharing mock roots with other
azldev operations:

```bash
azldev --unique-mockroot comp build -p curl
azldev --unique-mockroot comp render -p curl -p zlib
```

Each mock runner passes `--uniqueext` with an extension of at most 24 ASCII
characters: an abbreviated action, a component label of up to 12 characters,
and six random characters, for example `bld-curl-a2b3c4`.
An extension such as `rndr-abcdefghijkl-a2b3c4` uses the full 24-character limit.
Action codes are `bld` for builds (including advanced mock builds), `rndr` for
rendering, `qry` for queries, and `shl` for mock shells with or without packages.
These codes are never shortened further. Other actions use an abbreviated
command name.

Batch roots label the first component and include the component count when it
fits; otherwise they use the abbreviated first component without the count.
Labels use letters, digits, `_`, and `-`, never spaces.
The extension stays the same for initialization, commands, and cleanup of that
root; separate roots receive separate random suffixes. Without the flag,
mock's existing root naming is unchanged.

Unique-root commands also pass `--disable-plugin yum_cache` to disable mock's
shared yum cache. Commands without `--unique-mockroot` retain the configured cache
behavior.

Cleanup removes both the unique build root and its bootstrap root while preserving
shared caches. azldev checks `mock --help` for `bootstrap-cache` support before
cleanup: newer Mock versions can safely use `--scrub=bootstrap`; older versions
require `sudo` to remove only the bootstrap directory with the matching extension
after Mock finishes scrubbing the build root.
With `--dry-run`, cleanup skips capability and path discovery and previews the
scrub command without executing it.

The flag also applies to queries, custom source generation, and
`azldev advanced mock` commands. A unique `mock shell` session does not reuse a
previous session's root. To inspect a preserved unique build root, take its
`--uniqueext` value from the verbose command log and run
`mock -r <mock-config> --uniqueext <extension> --shell` directly; a new azldev
invocation generates a new extension.

## Related Resources

- [Components Reference](../reference/config/components.md) — component definition format
Expand Down
1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_advanced.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_advanced_mcp.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_advanced_mock.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_advanced_mock_build-rpms.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_advanced_mock_shell.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_advanced_wget.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_completion.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_completion_bash.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_completion_fish.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_completion_powershell.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_completion_zsh.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_add.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_build.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_changed.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_diff-sources.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_history.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_list.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_metadata.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_query.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_render.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_test.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions docs/user/reference/cli/azldev_component_update.md

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading
Loading