Bamboo 6.4 release notes
A complaint we often heard from teams using Bamboo was that there's limited self service in agent capability management: in order to install new tooling, one needed administrative privileges on the agent or the agent had to be to run with administrator rights (to install dependencies during build). Neither option was ideal: the former incurred administrative overhead, the latter was risky and would likely cause problems for subsequent builds running on the same agent.
With Bamboo 6.4, you can decide to run the build (or deployment) in a Docker container. This allows you to isolate the build process from the environment it runs in. There are several benefits to doing that:
- Increased security: you have strict control over resources the continuous integration (CI) process has access to,
- Improved CI reliability through isolation: the environment used to run the build/deployment is recreated and destroyed each time you run your builds - there are no stale files or processes left behind once the build is finished,
- Self service: additional dependencies can be installed during the build with no impact on subsequent builds.
If you want to learn more about Docker Runner, see our documentation.
Force-stop your hanging builds
Build monitoring mechanism of the Hung Build Killer plugin becomes native in Bamboo 6.4. This mechanism allows you to automatically stop any builds which, based on the criteria you set, are considered hanging.
Force-stop builds configuration applies globally. To overwrite its functionalities on lower levels, you can do it from the plan-level configuration.
To disable or change default Bamboo build monitoring settings, just go to > Overview > Build Monitoring.