Ulrich Kuhnhardt [IzymesCo] Atlassian Partner

@Nikki Zavadska _Appfire_ - how did you guys work around the problem? We have a similar problem with a read_only CF that's controlled by an issue property. Thanks, Ulrich

Hello there with your implementation of RepositoryMergeCheck comes @Override public RepositoryHookResult preUpdate(@Nonnull PreRepositoryHookContext context, @Nonnull PullRequestMergeHookRequest mergeHookRequest) { // get merge strategy by id Optional<String> mergeStrategy = request.getStrategyId(); ... } There you can…

Awesome - thanks for sharing

When you say "remains in git" - do you mean in your local repository on your workstation? If so - that would be normal, the remote (Bitbucket) will not make any changes on your and other users workstation. You and others will have to 'clean up' local branches. I found this article very helpful. Hope that helps, Best,…

Hi Rob, welcome to the community! If I understand your question correctly you are looking to block pull requests that would result in a non-trivial merge, i.e. both source and target branch had independent commits? As far as I know there is no such merge-check built into BB Cloud. Here is a ticket for Atlassian to allow…

Bit late to the party - but look at this solution https://community.atlassian.com/t5/Jira-questions/Re-Re-JIRA-REST-API-how-to-retrieve-issues-of-a-speci/qaq-p/964057/comment-id/309237#M309237 The key is to use /rest/api/2/search....

Looking forward to Percept.AI integration APIs for JSM apps. Tapping into an AI engine without data-egress has a huge potential for the app ecosystem. We have started with AI Insights for JSM to bring the benefits of AI to JSM - imagine the security and cost benefit when using JSM's own AI!

Great work, Remie! And a huge thanks to CS contributions in the partner slack channels, sometimes acting as the 'canary' to changes in the ecosystem, LOL!

I suggest the following approach to accomodate your use case: 1. Enable repository merge-check and require a minimum of one reviewer approval 2. Add a suitable post-receive hook to your repository from the MP (click the 'Add hook' button in your repository settings >> hooks >> Add Hook) (#1). The hook should un-approve…

Hi Irina, I understand that after a pull request's target branch revision changed (it has been rescoped) you would like to block it from merging? Can you clarify what 'build for pull request' means for your use case? It's possible to build and test for the _source_ revision of the PR or the the _target_ revision. You can…

Thanks for sharing, this is good news. I have a question as to whether the project settings sidebar is available as a location for apps to create their own project-level settings page content. Can you point me to the module (adminPages?) and location in app descriptor schema? https://api.bitbucket.org/connect.json Thanks…

Hello Joao, Welcome to the community! The feature you are referring to is for Bitbucket server/datacenter. This type of Bitbucket runs on your own infrastructure, you'd be hosting it yourself. Telling by the screenshot you're looking at Bitbucket Cloud, the SaaS version of aforementioned Bitbucket server/dc. The feature is…

@Tinker Fadoua @Atif Hassan On top of what @Tinker Fadoua suggested, you can keep your local feature-b2bapi branch, make the suggested changes in your IDE and then $ git commit -am"implemented review changes, or any commit comment" $ git push This way the existing pull request source branch (your feature branch) gets…

Thanks for sharing. Couldn't resist and tried this out ;) 2 Observations: 1. Node 2 doesn't start up while Node 1 has the shared home locked 2. Trying to start Node 2 after Node 1 starts up kills Node 1 bb_node_2_1 | 2022-01-20 02:43:02,661 INFO [main] c.a.b.i.b.BitbucketServerApplication Started BitbucketServerApplication…

Hi @Aaron Patterson , welcome to the community! I understand that you would like a bitbucket cloud server-side pre-commit checker that would validate commits pushed to remote. Unfortunately there is no such functionality in BB Cloud that would match the repo pre-commit hooks we all use & love in Bitbucket server. Here is…

The other party's workspace/project/repository issue tracker must be public to allow you to create tickets there. Check with the other party and get the link to their issue tracker.

I second @Dave Theodore [Coyote Creek Consulting] simple approach. Git is a DVCS and the local repository is an exact copy of the remote. The idea is to clone the full repository to a local machine, just like the codebase you’d be working on and then push it to a new (Bitbucket cloud) remote. Make sure you push with git…

Hi @Bert Oost , we've will have a cloud version of Workzone for Bitbucket available as beta in the next couple weeks. Please send me an email (info at izymes dot com) to discuss details and get access to the beta version. Best, Ulrich

Thanks for sharing your success recipes! Cheers Ulrich

Thanks for sharing - look interesting. Is the script option Java or JS or both?

I don't think prioritizing build results is possible out of the box with Bitbucket. Could you create a scenario where the main src changes and each test set create a separate pull request? If so - then you can use Organizr for Bitbucket to create dependencies between the test set pull requests and the main pull requests in…

Hi Michael, while best practice is to review and merge small change sets often, you could merge changes from 'feature' and 'bugfix' branches to your 'develop' branch and then create a 'release' pull request from develop to your 'release' branch and review the code then. Any updates and review feedback can flow into…

Bitbucket Cloud would need a pre-commit checker to validate references to Jira tickets - https://jira.atlassian.com/browse/BCLOUD-10471 Please vote! @Shana can you advice on a timeline when this check will be available? Thanks, Ulrich

@Raphael Viana You can make a Bitbucket REST API call (via curl or postman) to enable/disable specific hooks programmatically. 1. GET your repo hook keys via /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/settings/hooks 2. PUT request for hook to be enabled (DELETE disables the hook)…

... forgot to mention, Workzone does not require a 'build key' in its configuration for build result merge-checks and auto-merge.

The build result API for a certain commit as per REST API spec [1] can have the following payload: Example { "key": "TEST-REP123", "state": "SUCCESSFUL", "url": "https://bamboo.url/browse/TEST-REP1-3", "buildNumber": "3", The required build form lets you configure a merge-check based on successful build results for * a…

Awesome - thanks for sharing your solution.

We are working on an app-based solution for BBCloud that we hope to release at the end of this year. Please reach out to ulrich at izymes dot com if you want to discuss details.

Looks great! If a person works on more than one task, would the height of the bar adjust according to the percentage of time for each task? Are there over-load or under-utilised indicators for team members?

Hi Dave, I understand you have a variable number of builds that pass depending on the depth of code changes. It would be good to have a configurable merge check that adjusts the number of required builds according the file paths in the PR changeset. Unfortunately custom merge checks are not available (yet) in BBCloud…