Skip to main content

Output

Output

Recommended

Learn what information Custy reports after removing obsolete backup files.

Commandcusty cleanup backups

Category

Maintenance

Quick Command

custy cleanup backups
cleanupbackupoutput

Overview​

After Backup Cleanup completes, Custy summarizes the operation and reports how many backup files were processed.

Depending on the project state, the command may remove obsolete backup files or report that no cleanup was necessary.

Command Output

Example output produced after running the command.

Successful Cleanup

Backup Cleanup completed successfully.

Terminal
text
🧹 Cleaning up backup files...
→ Cleaning commit backups (keeping 10)
→ Cleaning tag backups (keeping 10)

✓ Pipeline completed successfully!

Backup Cleanup Output

Backup cleanup output
Example CLI output after Backup Cleanup removes obsolete backup files.

Successful Cleanup

When Backup Cleanup succeeds:

  • obsolete backup files are removed,
  • recent backups remain preserved,
  • the configured retention policy is respected,
  • the operation completes without affecting project source files.

No Cleanup Required

If the number of existing backup files is already within the configured retention count, Custy completes successfully without deleting any files.

This is considered a normal outcome rather than an error.

Dry Run Output

When using the global --dry-run option, Custy reports the cleanup operations that would occur without deleting any backup files.

This allows you to verify the cleanup behavior before making changes.

Pipeline Integration

When Backup Cleanup is executed as part of a workflow pipeline, its output appears alongside the other workflow stages.

The cleanup summary reflects only the Backup Cleanup stage while the pipeline continues with the remaining workflow steps.

What's Next?

If Backup Cleanup does not behave as expected, continue to the Troubleshooting page for solutions to common cleanup problems.