Comments
-
Jexo Monday morning coffee saves me HOURS on reading up on all the bits and pieces of news and announcements! :bigfan: Ulrich
-
I would like to expand on @Mikael Sandberg 's response. 1. If you have an existing pull request to master in Bitbucket you can merge it with the following REST API command https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/pullrequests/%7Bpull_request_id%7D/merge…
-
Congratulations - this is indeed an achievement you guys can be extremely proud of!
-
Thanks for sharing - good news that the move from the existing data-center to "true cloud" is complete with good or better performance. We at Izymes feel inspired to bring more enterprise features (as ACE apps) to Bitbucket cloud to enable enterprise Bitbucket DC customers to migrate eventually. We have had numerous…
-
Hi, I assume this is a developer question. You may get more help in the actual Bitbucket (server) developer community here: https://community.developer.atlassian.com/c/bitbucket-development/bitbucket-server/14 While the /dashboard endpoint returns the user specific set of pull requests across the instance - the…
-
Have you considered separate repos and deploy pipeline for each component (microservice?)? To me that seems to give you best flexibility.
-
Thanks for sharing. Your article makes CQL more approachable.
-
Is there a way you can suppress Jenkins sending "build" results to Bitbucket for job 2 and 3 in the job configuration? Or only configure build results being sent for job 1..
-
Hi Sayan, I would like to understand your scenario a little better. What do you mean by " we first merge the changes to qa branch after extraction from dev to bitbucket " Do you want to achieve selective deployment of components or selective merging of components to qa and prod branches?
-
Hi Mansur, unfortunately I don't know the answer - but here is the developer community for BB cloud [1] where you can post your question - and hopefully get a quick response [1] https://community.developer.atlassian.com/c/bitbucket-development/bitbucket-cloud/13
-
Bitbucket server project or repo settings let you define merge conditions, including the number of successful builds required. If the condition is not met, the merge button should be disabled. Internally Bitbucket performs all merge-checks [1] sequentially and if one or more fail the PR can't be merged, i.e. the…
-
The elastic search version for Bitbucket 7.6.3 is <elasticsearch.version>7.5.2</elasticsearch.version> How do I find the ES version? Download Bitbucket sources [1] via my.atlassian.com (you need a license to be able to access sources) for the Bitbucket version. Unzip and look in bitbucket-parent/pom.xml for most external…
-
PullRequestOpenedEvent is not a repository event of any sort that you can write a hook for. It's a simple event. Pull requests are glorified diffs that you can interact with through the webui. For this event handler to be configurable you don't have the convenience of the configurable hook system. You would need to add…
-
Sometime git 'discovers' a merge conflict even when both sides have identical code. Your best option is to resolve the conflict locally within an IDE or via git command line. Here is a really good tutorial from Atlassian - https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts If you choose to use git…
-
Would it be possible to move the event to lunchtime PST? We're in AU and there's no comparable event in our timezone. Thanks for considering, best Ulrich
-
What should such a report look like? What kind of stats do you want to report on?
-
If it is an option I suggest to create a versioned library or some sort of versioned artefact out of common that is consumed by Main. Main can choose which version of Common it needs. This way Main and Common can be maintained independently.
-
Yes - your CI system would make test results and stats readily available. I assumed that you need to 'count' tests to report on increased test coverage/count?
-
Thanks Cassie - access requested.
-
I don't have a direct solution - but what about parsing test result files / reports?
-
Great question, although I would have put 3 exclamation marks (!!!) in the title. Here is the ticket that tracks a request to allow BBC apps to implement custom merge-checks https://jira.atlassian.com/browse/BCLOUD-19885 Please vote and watch for updates. I understand that this is not the actual solution you're looking…
-
If it is an option you could block the user from the whole repository via repository permissions.
-
I can see how this relates to your previous question. The repository owner may choose to implement a policy (see above) to delete merged branches right after they have been merged. As this only happens on the server, but not on the developers' machine, developers can still maintain a local branch, if they choose to. Then…
-
Great question/request. There are a few ways to achieve this. 1. When a PR is merged Bitbucket Server offers to delete the source branch after the merge. 2. Add an existing hook by clicking 'Add Hook' in your repo settings [1] and find a suitable hook on the Atlassian Marketplace 3. Write your own PostReceiveHook (called…
-
Thanks for posting. Very interesting and detailed.
-
@Cassie Mayes - one of the community leaders I was able to contact talked about a Trello board for community leaders. I'll try to find out - are you aware of such a board? Or perhaps vendors can use this board to submit their presentation suggestions?
-
I can't directly provide a solution for Bitbucket core, however Workzone for pull requests lets you define pull request reviewer groups on project and repository level. Reviewer groups are based on your AD groups. Workzone also offers you to add group-quota merge-checks so you could configure how many approvals per group…