Deployment Log Retention Limits in Bamboo Global Cleanup

Goal: ensure that logs from failed deployments remain accessible long enough for engineers to perform a thorough post‑mortem analysis.

Constraint: Bamboo’s global log‑cleaning schedule, configured under Administration > General Configuration > Log cleaning, applies a single retention period to every deployment log; once that period expires the log is removed from the Deployment > Results page and the corresponding file is deleted from the Bamboo home directory, and the product provides no per‑deployment override or advance warning before deletion.

Uncertainty: whether administrators can protect individual failed‑deployment logs from this cleanup or receive a notification when a log is about to be purged.

Is there a way to exempt specific deployment logs from the global log‑cleaning schedule? Can Bamboo generate a notification when a deployment log is approaching its retention limit? Does the product support a per‑deployment retention setting that overrides the global cleanup?