-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
2
-
Currently, it is possible to bring Bamboo server down (if live logs transmission is on) by producing a huge build log file. Hung detection mechanism does not work in this case since the build may be doing smth in an infinite loop and produce output.
It would be nice to have some configuration that would prevent the system (both Bamboo server and agent) from going down in such cases, i.e. be fault tolerant. A mistake in code should not make an entire system (or a remote agent) unresponsive due to No space left on device and other issues related to handing huge log files.
The suggestion is to have build logs file size caps in place and either stop writing output to a log file or mark the build as hung to let Bamboo server stop it.
- details
-
BAM-16357 Allow Bamboo to monitor build log size and stop builds when their logs grow too large
- Gathering Interest
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.
Kind regards,
Bamboo Data Center