8.4. Pruning builds

In order to prune builds that are no longer required by the system due to age and status, administrators can run the following command:

oc adm prune builds [<options>]

$ oc adm prune builds [<options>]

Copy to Clipboard

Toggle word wrap

Expand

表 8.3. Prune builds CLI configuration options
Option	Description
`--confirm`	Indicate that pruning should occur, instead of performing a dry-run.
`--orphans`	Prune all builds whose build configuration no longer exists, status is complete, failed, error, or canceled.
`--keep-complete=<N>`	Per build configuration, keep the last `N` builds whose status is complete (default `5`).
`--keep-failed=<N>`	Per build configuration, keep the last `N` builds whose status is failed, error, or canceled (default `1`).
`--keep-younger-than=<duration>`	Do not prune any object that is younger than `<duration>` relative to the current time (default `60m`).

To see what a pruning operation would delete:

oc adm prune builds --orphans --keep-complete=5 --keep-failed=1 \
    --keep-younger-than=60m

$ oc adm prune builds --orphans --keep-complete=5 --keep-failed=1 \
    --keep-younger-than=60m

Copy to Clipboard

Toggle word wrap

To actually perform the prune operation:

oc adm prune builds --orphans --keep-complete=5 --keep-failed=1 \
    --keep-younger-than=60m --confirm

$ oc adm prune builds --orphans --keep-complete=5 --keep-failed=1 \
    --keep-younger-than=60m --confirm

Copy to Clipboard

Toggle word wrap

注意

Developers can enable automatic build pruning by modifying their build configuration.

Additional resources