Microsoft Teams Bamboo Connector Guide explains how to setup, presents demos and troubleshooting information.
Atlassian Bamboo Data Center is supported. Please check Microsoft Teams Bamboo Connector on the Atlassian Marketplace.
You can read more about connecting Bamboo and Microsoft Teams at Move Work Forward.
The App is available at Atlassian Marketplace - Microsoft Teams Bamboo Connector.
Atlassian Bamboo is a powerful continuous integration and delivery tool that helps development teams automate their build, test, and deployment processes. With the integration of Microsoft Teams, teams can stay up to date on the state of their build pipelines and receive all types of notifications in real-time.
One of the key benefits of using Bamboo and Microsoft Teams is the ability to track the progress of build pipelines and receive alerts when there are any issues or failures. This helps teams stay on top of their development cycle and identify problems as soon as they arise, reducing the time it takes to fix issues and get code into production.
In addition to notifications, Bamboo also allows teams to create and manage build specs directly and integrate build plan Microsoft Teams notifications.
Finally, Bamboo's integration with Microsoft Teams also includes access to build output artefacts directly from within the Microsoft Teams interface. This means that teams can quickly and easily access the results of their builds, including test results and other important information, without having to switch between tools or navigate away from their primary work environment.
Overall, integrating Bamboo and Microsoft Teams helps teams save time, reduce development cycle time, and stay updated on the state of their build pipelines. By bringing all of these capabilities together in a single, integrated platform, teams can work more efficiently and effectively, helping them to deliver high-quality software faster.
General Microsoft Teams Bamboo Connector demo
Bamboo Specs mode
Frequently Asked Questions
You can find the frequently asked questions on the Microsoft Teams Bamboo Connector product page.
Go to the Microsoft Teams channel configuration and add an Incoming webhook connector.
Find Incoming Webhook and add it.
Put the name as Bamboo and set the Bamboo logo.
Save the configuration that will generate the webhook URL. Copy it to the clipboard and save the Incoming Webhook.
Bamboo Build Plan configuration
Navigate in Bamboo to the build plan you want to receive notifications from.
Go to the Notifications tab.
After you add the notification setting, you should see the screen below where you can configure the Microsoft Teams webhook URL and other settings.
Below you can add additional filters on build progress events.
After you have saved the notification configuration it should appear in the list of notificaitons.
From now on, your channel in Microsoft Teams will get notified, and you should see something similar.
Bamboo Build Task configuration
Another option is to use Atlassian Bamboo build tasks to notify Microsoft Teams channels about particular events. You can also use all Bamboo variables inside the message.
The resulting message may look similar to the following.
Bamboo Java and YAML support
Please make sure that you have the latest App version, we fix issues pretty quickly, and there is a chance that your problem has been fixed.
Go to Bamboo administration > System -> Log settings. Then add the app key (see table below) for "Classpath" and choose DEBUG as "Type". You should then see log messages of the app with severity DEBUG either in your Bamboo Server log (BAMBOO_HOME/logs/atlassian-bamboo.log) or in the Remote Agent server log.
The app namespace is com.moveworkforward.bamboo.microsoftteams.notifier
The additional guide from Atlassian.
Download the support zip
You can send us the support zip, which contains the log files. You can download it following this official Atlassian documentation.
You can create a Jira Service Desk support request with all information you can gather, please include the screenshot of the configuration (please don't worry about the webhook URLs, we won't store or use them) and the logs or errors you could find in the browser or on the server-side.