Australian company Atlassian offers Bamboo, a continuous integration server.
N/A
Bambu by Sprout Social
Score 9.2 out of 10
N/A
Bambu is a social media marketing tool from Sprout Social that leverages employee advocacy. It allows users to organize and encourage distribution of company blog posts, press releases, news and articles, thought leadership, and customer case studies through employees' personal social networks on Facebook, Twitter, and LinkedIn. There are three main use cases for Bambu: Marketing, HR, and Sales. In terms of Marketing, Bambu aims to leverage employee advocacy to increase brand awareness…
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.
Routinely sharing job postings from Bambu by Sprout Social to LinkedIn, using the canned content our Marketing team provides and revising so that it "sounds like me" prior to sharing on LI. Cadencing my content shares for the week in the "Scheduling" option Creating a new link to share content via Bambu by Sprout Social to LI, to position myself as a thought leader in my space
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.
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.
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.
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
It was similar in that it helped us push prewritten messages out to our team, but the UX/UI was far more dated and not as intuitive. It's mobile app also wasn't very useful; made it difficult to edit messages and would constantly need you to log back in. The two things GaggleAMP had over Bambu however was more comprehensive analytics and the ability to automatically push out social posts
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.
The social amplification effects of our employees sharing brand content helped us achieve a 400% increase in website visits following our re-brand.
With some "Executive nudging" when we announced that Bambu would be used as our internal comms tool, and that we would only be sharing real-time updates via the mobile apps push notifications, we were able to double the # of employees who use the App in addition to the desktop application. Mobile users aside, another positive side effect of using Bambu as an internal comms tool is that it exposes users (the non-social butterflies who don't like to share) to all other content that has been curated into the system and has helped garner more social impressions.
The majority of our employees come from the BabyBoom/Gen X generation and didn't come of age in the world of social media, which has presented some challenges in user adoption rates.
