We have Merge Check enforcing 2 successful builds. Let's say there are 3 types of builds: Build, Sanity, and GUI-Sanity. All the 3 happened and reported to BB as follows:
- Build = SUCCESS
- Sanity = SUCCESS
- GUI-Sanity = FAILURE
Bitbucket in this case does not let us merge because 1 build failed. So is it necessary to all the build should succeed.
Hi Pankaj! Can you confirm that you followed the right steps at Suggest or require checks before a merge? Note that if you're Premium, there's an option to avoid the pull request to be merged if not all the builds are successful. Are you on Premium?
Also, can you send us a screenshot of the settings so we can see everything is right?
If this is still not working as expected, we might need to get more info like some logs for example. Let us know how it goes as I'll need to create a support ticket for you in that case.
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot