Bamboo for Continuous Deployment and Continuous Integration
December 14, 2018
Bamboo for Continuous Deployment and Continuous Integration
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Bamboo
Our software development department uses Bamboo for Continuous Deployment and Continuous Integration. We use also its integration with Bitbucket and Jira, which allows control and visibility through the entire flow: from the Jira epics/stories/tasks to the revision control version number in Bitbucket to the build number in Bamboo. In all our environments: development, QA, preproduction and production.
- Continuous Deployment - you can use Bamboo to automatically build and deploy whenever there are changes in the source code.
- Continuous Integration - by integrating the automated tests and the integration tests before deploying you make sure you know immediately if the latest code fits into the whole scheme of apps.
- Integration with Jira and Bitbucket.
- Flexibility with the program language used for builds: Maven, Ant, PowerShell, any command line tools.
- When you have more complex applications using different technologies, it can be a pain to initially set up all scripts for deploy and test.
- Flexibility to use many build technologies at a lower level comes also with a problem that sometimes it is difficult to see from the interface what exactly is wrong with the build if the scripts are not handling errors very well. This can take lot of time to debug.
- May take some time for the team to learn the product and use it at its full potential.
- It helped us achieve the Continuous Deployment and Continuous Integration goals for our applications, a huge milestone that saved a lot of time for developers in making the builds and deployments and saved time for QA in running the automated tests.
- Helped with DevOps: we moved the formal approval from the email to the system and allowed the approver to actually push the button for the production deployments.
- Biggest positive impact of using Bamboo is that it improved our response time to customers and increased the frequency of our deliveries to them.
We used Jenkins before for our projects.
While Jenkins has an extensive plugins list that makes it more flexible to integrate it with other tools, we switched to Bamboo for nicer User Interface but mostly for the seamless integration with Jira and Bitbucket. Also Bamboo has more built-in features compared to Jenkins.
While Jenkins has an extensive plugins list that makes it more flexible to integrate it with other tools, we switched to Bamboo for nicer User Interface but mostly for the seamless integration with Jira and Bitbucket. Also Bamboo has more built-in features compared to Jenkins.