bamboo 5.7 removed legacy stash notifications; will the plugin 'workzone' function without them?

[john livingston]

Will the workzone plugin function with bamboo 5.7? Stash notifications have been removed from bamboo 5.7.

https://confluence.atlassian.com/display/BAMBOO/Bamboo+5.7+Release+Notes

[Ulrich Kuhnhardt [IzymesDev] · Accepted solution]

Workzone monitors the calls to the REST Resources Provided by the Atlassian Stash Build Integration Plugin. As far as I know Bamboo 5.7 is POSTing build results to all connected Stash servers.

[john livingston]

Thank You, Ulrich. We are running 5.6 in production and needed confidence prior to removing notifications in preparation for a 5.7 upgrade. At this point, we have removed notifications and our process is functioning as expected.

[john livingston]

Hello Ulrich, We have disabled Stash notifications in Bamboo 5.6 and observed the following This sequence starts the merge process. 1. pull request created in Stash 2. bamboo build/test completes 3. changes approved by reviewer This sequence fails to start the merge process. 1. pull request created in Stash 2. changes approved by reviewer 3. bamboo build/test completes We have since re-enabled Stash notifications to ensure both sequences are handled correctly. The Stash notification we have re-enabled is "All Builds Completed." This looks similar to - https://bitbucket.org/izymesdev/workzone/issue/46/auto-merge-seems-to-happen-only-after-user

[Ulrich Kuhnhardt [IzymesDev]]

We have encountered some problems with Bamboo 5.7 when an OAuth based application link is configured between Bamboo and Stash.

Problem

The POST request from Bamboo seems to be authenticated via app-link OAuth challenge and is not associated with a stash user. When Workzone tries to find open pull requests to match the commit hash it needs to do this with an actual user logged in.

Workaround

• Configure outgoing Bamboo Applink to Stash using Basic Auth (username/password)
• Configure Stash incoming Applink from Bamboo using Basic Auth as well.
• Configure Bamboo plan/branch to notify Stash.

[john livingston]

We are currently running Bamboo 5.6. Does this problem exist in Bamboo 5.6 as well? We have both OAuth and Basic Auth configured. Will the workaround function if both are configured? Bamboo 5.7 release notes indicate Stash build status notification is removed. Is it still possible to configure Bamboo plans/branches to notify Stash in Bamboo 5.7?

[Ulrich Kuhnhardt [IzymesDev]]

Hi John - I've confirmed the following to work # In Bamboo app links configure *outgoing* Authentication as basic auth like http://cl.ly/image/3F3W2K2m380u # In Bamboo plan configure notifications for Stash like http://cl.ly/image/2j3l450x2238 . Note the hint to configure *Basic Auth* between Bamboo and Stash # In Stash app links configure *incoming* connections as basic auth like http://cl.ly/image/3C3t2J15102E You can set up a staging instance of Bamboo 5.7 and connect it with a Stash test project to test out auto-merging.