There once was a build plan, and a build failed in it. (which was expected)
I destroyed that build plan, and created a new branch build plan under a different parent build plan.
That build was green.
But, the pull request in stash, will not enable the merge button cause it still has a link to a bad build.
(and a link to the new green successful build)
Is Stash saving bamboo build results? I would have thought that the Stash Pull request page would be grabbing Bamboo's build results on the fly.
How do I tell Stash, to get some fresh results from Bamboo?
Stash receives build results as they happen and they are grouped by a build-key (the latest result is taken to be the one applied for merge checks). It sounds like your new build plan has a different identifier.
There are a few options available:
True, the new build plan has a wholly different build plan ID.
To work around this issue we've done what your 3rd bullet item suggest: manually merging locally, then pushing to the remote. Then the pull request magically disappears.
That link about using REST and JSON object looks interesting. I will try that the next time this situation comes up, which will be often. Actually, I tried it last night as the problem occurred again. It worked. Very slick.
Thanks for the quick and accurate reply.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot