Likelihood to Recommend
If you value integration over cost, Bamboo is clearly the way to go. It offers tight integration to the rest of the Atlassian suite, and when you need traceability from issue to build, Atlassian is the right way to go. However, if you find yourself needing to save on costs, you may consider taking an approach of rolling your own build system with open source alternatives, such as
, if you don't [mind] putting in a little extra elbow grease.
Read full review
Gradle is an ideal tool to build an application that is complex and/or distributed. It is well suited for builds that use a CI engine such as
or Bamboo, and a repository such as Artifactory.
Read full review Pros Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately. Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well. Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful. Read full review Build Cache - Enables quick build on dev machines Supports multi project builds - enabling modular architecture Customizable build tasks Support for multiple JVM languages Read full review Cons Extremely hard barrier to entry for non-backend developers Blackbox makes it hard to customize functionality The inability to add features without breaking core functionality No cloud solution Tasks cannot be put in if/else statements No clear right way to form build plans Read full review Still under development, not as mature as Maven Build files aren't as easy to follow because they are so loose The community isn't as large as Maven Read full review Usability
Bamboo was fairly easy to navigate but in the end it always felt as if it was developed as a bolt-on and not a true group up user interface. There were multiple ways to get to everything and the path was never the same. So it was difficult for users to really get a feel of how to use the application.
Read full review
Gradle's language construct is good
Read full review Performance
I have tried to use Gradle for projects several times in the past, but there is just so much work in maintaining the build file that it quickly becomes untenable. I have been using Maven for many years, and even though the build file can be complex, it works without maintenance between releases.
Read full review Support Rating
Support for Bamboo has started lack a little over the years. Atlassian has been moving more towards
Pipelines and away from the on-premise install of Bamboo. While the tool is still great, it may take a little bit of time to get a question answered by official support.
Read full review
Gradle has been an excellent tool for Android development. It has helped us create multiple versions of the app for different environments. It also takes care of all the packaging needs in the background without having to write all the code related to that. It is a no brainer to use Gradle with Android applications.
Read full review Alternatives Considered
We selected Bamboo because its capabilities to integrate with other
and in some useful scenarios with
. Also, we found these pros important for us: great user interface, easily agent deployment, Docker compability, simply to maintain / manage, and straightforwardly integration with different notification platforms
Read full review
SBT works fine for Scala but when I tried to use it with Java it was hard to configure and I gave up. Maven is awesome but the pom.xml file tends to be really big which makes it hard to read. Grunt is suitable only for js projects.
Read full review Return on Investment 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. Read full review In a distributed development environment, once we established a strong CI/CD model, Gradle proved to be a great choice to automate the various processes. Gradle also provides much flexibility, which is essential in today's development environment. The important benefit is that the CI/CD engineers can support development's needs quickly and reliably. This in turn supports faster testing and deployment, which generates higher ROI. Read full review