Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-19887

Kill child process spawned during build

XMLWordPrintable

    • 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.

      When using flow-bin, as an example, multiple child processes are spawned during the build that do not get cleaned up when complete. While, in the case of flow-bin, this is a reported bug (wish an open pull request for a fix), the same behavior can be seen with anything that does not clean up after itself.

      In the use case that spawned this request, our customer provides Bamboo as a service to their customers and they can opt to use tools such as flow-bin that then leave child processes behind and eventually cuz the agent to run out of memory an crash. It would be preferred if there was a cleanup process to ensure that there are not errant child processes left to consume resources.

      —

      Workaround:

      Since 6.4 "Force stop hanging" is bundled into Bamboo and it is used to kill child processes that hang.

      https://confluence.atlassian.com/bamboo/bamboo-6-4-release-notes-946020272.html#Bamboo6.4ReleaseNotes-Force-stopyourhangingbuilds

       

            [BAM-19887] Kill child process spawned during build

            Victor Debone added a comment -

            This is default behaviour for Bamboo and we provide "Force stop build" feature to kill child processes that stay around after the tasks are completed.

            Victor Debone added a comment - This is default behaviour for Bamboo and we provide "Force stop build" feature to kill child processes that stay around after the tasks are completed.

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 24 March 2020

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,

            Bamboo Team

            Martyna Wojtas (Inactive) added a comment - Atlassian Update - 24 March 2020 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Bamboo Team

              Unassigned Unassigned
              bsewell@atlassian.com Bob Sewell (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: