Continuous Integration and Continuous Delivery Tool “Bamboo”
- on-premise
- Continuous Integration (CI) Server
- Checkout, build, and deploy from repositories Automation
What is Bamboo?
Continuous CI tool. It can automate checkouts, builds, and deployments from repositories. It facilitates collaboration among team members including project managers, developers, testers, and system administrators by connecting test results, build status, commits to source repositories, and issues.
Main Features
Build and Deploy Automation
Automate checkout, build, and deployment from source repositories. Parameters can be defined for each environment (development, test, production, etc.) to manage deployment to each environment.
Interfaces to tools such as Ant, Maven, Grails, Tomcat, MSBuild, etc. are provided for easy setup. For tools that do not have interfaces, scripts can be created and used.
You can choose to start the process by starting a timer, committing to a repository, or other methods. It is also possible to invoke the process from an external system via a remote API.
Supported repositories
CVS, Perforcem, Git, Subversion, Mercurial build tools are not included in Bamboo. You need to prepare them separately.
Combination with Jira
It is an Atlassian product, so it is highly compatible with Jira.
The build screen displays links to related issues.If a build or test fails, you can raise a Jira issue from the failed result.
Combination with Stash
When combined with Bitbucket, Bamboo will search Bitbucket repositories. It is easy to set up as you only need to select from the list. It also simplifies the setup of user authentication, which can be a hassle to operate.
Bamboo detects and follows the creation of branches in Bitbucket, so there is no need to modify Bamboo tasks every time a Git branch is added.
Code Coverage
Finding missing cases in test cases through code review can be difficult, but when combined with Clover, you can output a Code Coverage report. You can traverse packages, classes, and source code to find code that is missing tests, or methods and branches that should be tested next.
Other Functions
Report Function
The number of builds, the status of failures, and the time taken to deal with build failures can be tabulated and visually confirmed.
Notification function
Notification can be sent via e-mail when a build is executed. Notification events (build execution, failure, success, etc.) and recipients (user-specified or group-specified) can be customized.
Teams can use burndown charts to track progress against sprint commitments.
Introduction of CI Server Bamboo
January 29, 2011
CI servers have been getting a lot of attention lately, and they can be used in two ways: to help developers get into a good working rhythm, and to detect problems quickly and efficiently. Build, Test, CI Server Comparison ThoughtWorks' CI Feature Matrix is a very good summary. There are so many CI servers out there. Hudson, which is often used in Japan, is also listed in the comparison table.
Comparison of Plans
- Configuration in Code
- Jira integration
- Bitbucket integration
- Cold Standby High Availability
(active-passive) - Build resilience
- Project level resources
- SAML / SSO
- DC App Program
-
- ―