Ulrich Kuhnhardt [IzymesCo] Atlassian Partner

Hi Lee, you can't trigger a build in bamboo via webhook the same way you start a build from the UI (hence the XSRF failure). Here is a setup guide on how to trigger a post commit build from Bitbucket (Cloud) https://confluence.atlassian.com/bamboo/triggering-a-bamboo-build-from-bitbucket-cloud-using-webhooks-873949130.html…

Hello Andre, welcome! Based on your interest, start to follow some of the community groups or products categories. You can choose them from the top menu. If you have a specific question post it in the relevant group and you'll get a friendly community member or Atlassian staff member help you out in no time.

Love it! Does it have filters - for example to filter out Atlassian owned apps :D

Do I understand correctly Bitbucket is sending a webhook notification to TeamCity to trigger a build? The event payload should contain all the necessary details you need to identify the correct pull request. Have you talked to team city support on how to trigger the correct build for the event payload?

Correct, the repository group (not the AD group) needs to have members which are regular users with repo read permission. Then after typing the group in the reviewers field the members of the repo group should be inserted. In the above case the 'repo-dev-group' has the following members As I already mentioned if you want…

Hi Galit, it's Ulrich again :) The quick answer is no - pull request ids across repositories are not unique. May I use why you need a unique PR id? I know that the repo id is absolutely unique in the instance across all projects and repos. I suggest you create a combined 'id' or hash that includes both the repo id and the…

You may find that when you type the group name it may appear in the select dropdown - and when you select the group by clicking on it the members are added as individual reviewers You need to make sure that group members have sufficient permission for the repo, minimum is READ permission.

+1 on the remote pre-commit check hook. 

Atlassian Bitbucket team is investigating - keep an eye on https://bitbucket.status.atlassian.com/

Hi @Akash Ashok Kondekar , the only way Bitbucket cloud merge checks are enforced is when you are on a premium subscription. Perhaps you have upgraded to premium? Also have a look in the top right corner of the PR page under the 'checks passed' panel, it should show you which merge check is failing. Cheers, Ulrich

I'm wondering if app vendors should post updates here or in https://community.atlassian.com/t5/Apps-Integrations/ct-p/atlassian-marketplace ? While this here is categorized as a 'Group' and Apps&Integrations is categorized as 'Products' - there doesn't seem to be clear difference in scope. Could you please clarify scopes…

Atlassian has made a change to how Bitbucket cloud loads your first page. The first page load no longer links to your personal workspace. Now the last shared workspace you visited loads by default. Click on your avatar top right to switch between workspaces or see a list of all workspaces, including personal ones. Hope you…

Thanks for the insightful article.

Agree with the comment by @Saxea _Flowie_ - there are a few more apps that support your requirement: * Workzone for Bitbucket Cloud by Izymes (UI based configuration) * Code Owners for Bitbucket By Mibex Software (code based configuration) Please let me know if I can help you any further with your setup. Cheers, Ulrich

curl -u admin_user:admin_pw --request GET \ --url 'http://{baseurl}/rest/api/latest/repos' \ --header 'Accept: application/json' Here is the REST API documentation https://developer.atlassian.com/server/bitbucket/rest/v811/api-group-repository/#api-api-latest-repos-get

Hello Paul, welcome to the community! Have a look at the Bitbucket datacenter documentation - required builds merge check. You can define which target and source branches enforce a successful build. That should do the trick. If you don't have DC or want more detailed merge-checks you may use our Izymes Workzone tool to…

Hello Galit, welcome to the community. Short answer to your question: Yes you can! (see below) Out of the box Bitbucket server lets you create reviewer groups at repository level that you can use when you create a pull request. Note that reviewer groups are NOT AD groups that exist instance wide. While repository reviewer…

Here is what Chat-Gee-Pee-Tee thinks. Looks absolutely spot on.

Sounds very interesting! Have a look at https://www.atlassian.com/software/artificial-intelligence though.

Thanks for sharing! This is great, cc: @Sean Manwarring _Izymes_ !!

Congratulations - it's great to see a success story with Vanta. What was your price-point roughly (hours and fixed costs)?

Just out of interest - which app was the culprit? If it was Workzone please let me know. Best Ulrich // Izymes

Hi Andy, the Workzone approval rate or quota is a sort of fall-back option if no other merge-conditions are present. Defaults to 100% but you can set any count value or percentage. Clearly you have a required mandatory approval count - so there is not need to 'fall back' to a basic approval count or rate. Workzone should…

My previous reply assumes you have a Workzone merge configuration in place for the 'main' branch. Workzone needs to know what other merge checks it should perform. If you haven't already please create a minimal Workzone merge config for destination branch 'main' * Destination branch: main * Merge user: Leave blank if you…

Hello Andy, Thanks for reaching out. The solution to your problem is to make Workzone enforce merge checks. You can do this in either * global Workzone settings (in the BB admin area) for the whole instance * Project-wide in Workzone project settings > Properties * Repo-wide in Workzone repo settings > Properties Here is…

Hi @Claudiu Argeseanu - welcome to the community. You can rest assured that Bitbucket or git for that matter will not override changes already merged. Hence it is called a merge and not a write. Each merge is an atomic operation. Even if you were to write (push) to master git/bitbucket won't let you (unless you use the…

Hello @Dhananjay Salunke - welcome to the community! In Bitbucket cloud you can set up branch restrictions for any branch * On repository level * OR if you have a similar branch structure for repositories in your project(s) configure branch restrictions on project level Hope that helps! Best, Ulrich // Izymes 

Hi David, welcome to the community! I believe Bitbucket server/datacenter does not have file/path reviewer configuration. We have built Workzone to enable teams like yours to cover exactly this use case. You can define which reviewers need to review which files/paths and you can enforce required approvals for each…

Hi @Nishanth Korupolu As @Sachin Dhamale has mentioned you can define PR default reviewers in repository settings. The reviewers will be added to every pull request. Groups cannot be configured, only individual users. If you like to add groups as reviewers you can use an app like Workzone for Bitbucket cloud which gives…

Hi Lydia, Bitbucket uses git as the underlying distributed version control system (DVCS). You have a remote repo in Bitbucket and a local repo on your machine. Your local repo 'talks' to the remote repo via git commands. When you execute a git command and communication to the remote is required, the local machine needs to…