Goal
To eliminate deployment blockers caused by Jenkins disk space exhaustion and remove the requirement for manual Support intervention.
…
Context
As a Liferay PaaS developer, I want the platform to proactively manage Jenkins storage or provide me with the visibility to do so myself, so that my CI/CD pipeline remains reliable, and I never have to wait on a Support ticket to clear disk space for a critical deployment.
Liferay PaaS customers may encounter “low disk space” failures during Jenkins builds. While Liferay provides information on native ways to manage storage, these preemptive measures may fail to solve the problem because:
- Configuration gaps, as customers may not be aware of these settings or failed to find a configuration best suited to their deployment needs.
- Lack of visibility in the Cloud COnsole to warn a user.
Currently, once the disk is full, the customer is effectively locked out of their own deployment process. This creates a reactive support cycle where the only resolution is a manual, (potentially undocumented) cleanup by the Support team.
…
Proposed solution
Update the Liferay Cloud Console and underlying Jenkins stack to shift from manual intervention to an automated process where:
- The customer is provided clear visibility into Jenkins storage health so users aren’t surprised by failures.
- Automated cleanup or “self-healing” logic to prevent disk saturation (should this be autoconfigured and needs to be disabled?).
- a simple way for customers to trigger maintenance or resolve space issues independently via the console or LCP CLI.