ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Measuring a bottleneck before optimizing Bamboo plans requires separating build execution time from integration latency at the Bamboo-JIRA boundary. The integration relies on REST API calls to transition JIRA issues after a build completes. Behavior may differ between Bamboo Server/Data Center and Bamboo Cloud, and Elastic Bamboo agent startup is deprecated
Feature: Elastic Bamboo Agent Scale‑Down The goal is to ensure that when Bamboo reduces its elastic agent quota, no agent executing a build is terminated before the build finishes. During a scale‑down event Bamboo attempts to finish current builds, but there is no configurable timeout that guarantees a build will complete; the decision relies on an internal
For a low-traffic Bamboo Server deployment that uses AWS elastic agents, the goal is to choose an agent idle-timeout value that reduces compute charges without noticeably delaying build feedback. The uncertainty lies in the trade-off between the 30-90 second provisioning latency and the cost of keeping an agent running idle; build frequency can vary from a f
bamboo