• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Logs
    • 0
    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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.

            [BAM-21103] Mark builds as hung based on build log size

              Unassigned Unassigned
              c64f33b2bce3 Yevhen
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: