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
Jenkins , if you don't [mind] putting in a little extra elbow grease.
Read full review Receptive is very effective for multiple internal teams/department of a single product who need to scale their product feedback management effectively. We've been leveraging it for one of our products and it was so successful, that we implemented it with a second product. The main issue we ran into situationally with that was managing 2+ modules (products) in Receptive; it was a bit more difficult to present Receptive to two different customer bases/users (we couldn't change the appearance) and slightly confusing to do within the app (lots of filtering needed). I have heard that support of multiple modules is something that Receptive will likely be working on in the near future, so that's good news.
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 Easy collection of enhancement requests Linking to Jira tickets for development priorities Provides visibility for our customers into their priorities 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 Do not charge per user (we almost cancelled over that). Get rid of or make the assumption of time and money saved more realistic. 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 Support Rating Support for Bamboo has started lack a little over the years. Atlassian has been moving more towards
Bitbucket 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 The support team is great - responsive and helpful.
Read full review Alternatives Considered We selected Bamboo because its capabilities to integrate with other
Atlassian products specially
Jira Software ,
Bitbucket and in some useful scenarios with
Confluence . 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 We had
UserVoice prior to Receptive but it was just too clunky and extensive for our needs. It was less about automation and still very manual work to process feedback. It also didn't provide collaboration levels that we needed for our internal teams to work together.
ProdPad was a very clean tool but also didn't enable us to automate the process like Receptive does.
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 Able to tie costs to enhancement requests via Jira integration Read full review ScreenShots