Kristy Atlassian Team

I believe that the original question was for Bitbucket Server (see the tags), but your screenshot is for Bitbucket Cloud. You're best bet is to create a new question in the community.

Hi @pawan.mishra, this is only for Bitbucket Server / Data Center.

Hi @Serif Ciftcioglu , Can you please share what version of Bitbucket Server you are using? Also, what CI tool are you using? If you are able, some screenshots showing the problem and describing where you would like to see the builds would also be helpful. Thanks, Kristy Developer on Bitbucket Server

Hi @[deleted] , Can you please expand a bit on your problem? * Are you able to visit the Bitbucket Server UI through your browser? * Are there any errors in the logs? * What URL are you trying to clone from? For proper support you can open a support ticket here: http://getsupport.atlassian.com Hope that helps, Kristy

Hi @Marc Mantei , There are two options for you: Using a webhook and using a post-receive hook. If you would like your solution to be a microservice managed by you, then a webhook is the way to go. All you have to do is expose an endpoint for the webhook to trigger on push, and enable the Webhook in the Bitbucket Server…

Hi @Shravan Nagareddi , The error is most likely permission-related. How is your Jenkins instance authenticating with your Bitbucket Server instance? The easiest way to connect Bitbucket Server to Jenkins is to use Atlassian's official Bitbucket Server Jenkins plugin. You can read more about it here. Hope that helps!…

Hi @SANTHOSH KUMAR CHAKILAM , The new Pull Request you're referring to that has a sidebar is a feature of Bitbucket Cloud: https://support.atlassian.com/bitbucket-cloud/docs/try-the-new-pull-request-experience-in-bitbucket/. The pull request experience in Bitbucket Server/Datacenter was updated in 7.0, but does not have…

It seems that your code insight post doesn't have a 'result' field on the create report request. Otherwise it would show a "Passed" lozenge in the sidebar of that dialog. For example, it would look like this: What is the JSON payload that you are sending to Bitbucket Server? Does it have a 'result' field?

Hi @bfierz Code coverage has not been implemented as a core feature in Bitbucket Server yet. However, there is an API that can be consumed by plugins to provide this information. The plugin you linked is one such plugin that consumes this API, and it was developed by Atlassian. However, as you mentioned it is not…

Hi @Pastajello It is available but not documented because it is private API. This means that Bitbucket Server makes no guarantees about it - it might change in future releases of Bitbucket Server without warning. If you are making a plugin or something that is expected to be reliable, then you should not be using private…

Hi @Pastajello , The attachment REST API became publically available in version 7.0: https://docs.atlassian.com/bitbucket-server/rest/7.1.2/bitbucket-rest.html#idp192 All the best, Kristy

Hi @kranthi311 There is something wrong with your elastic search setup. There should be some error messages in your Bitbucket Server logs that would shed some light on this. I'm not sure if you are the administrator of your instance, but if you are then you can look in your <bitbucket-home>/log/atlassian-bitbucket.log to…

Hi @Kevin Reynolds The snippet generator should have a bbs_checkout step in there: You should then be able to fill out all the derails and generate the snippet for your Jenkinsfile Hope that helps, Kristy

Hi @Kevin Reynolds It appears that you've selected the wrong trigger. You need to select "Bitbucket Server trigger build after push" to get the webhook created. The one that you've selected is not related to our plugin. Regards, Kristy

In this case, I believe the question was about a pull request from a `release/` branch. In this case, you wouldn't want to pull the target branch into the source branch because the `release/` branches should always be behind the target branch

Can you help me understand what you think was missed? Do you mean missed in the Bitbucket Server branch model? Because its certainly possible to create a hotfix branch from a release branch and when that is merged into the release branch, the release branches will automatically cascade down into later release branches and…

Bitbucket Server does not have a 2.0 REST API. But the Bitbucket Cloud documentation can be found here: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/branch-restrictions

This would usually work for most branches, however the example that has been posted is for a release branch merging into master. Most of the time, there would be branch permissions set up to stop you from pushing directly to release branches so this approach may not work in those cases where you do not have permission to…

Hi @Akilesh DS Is it possible that you have whitespace changes? Can you please try turning on the 'ignore whitespace changes' setting in the diff to see if that affects what you see? Does the unified diff also show these lines as removed and added? Also, what version of Bitbucket Server are you running? Regards, Kristy

Hi @Wayne Bridgman You cannot override the project-level default reviewers in a repository. The way you understand it is correct - repository default reviewers are an additional requirement to the project-level ones. If the main purpose of the project-level default reviewers is to ensure that 2 people approve, then you…

Hi @Suporte IC Did the import successfully finish? Are you able to browse the code on Bitbucket Server without issue? If you're comfortable looking in the logs yourself, then you may want to look at the logs to see if there are any errors that may help diagnose this issue. However, your best course of action would be to…

Hi Mario, This question is specifically about the automerge feature of Bitbucket Server. Bitbucket Server does not support Mercurial, which is why the answer is git-specific. If you have a question about merge conflicts in Mercurial, I suggest that you create a new post for it and tag it as "Bitbucket" (not "Bitbucket…

Correct, however the pull request that has been automatically opened doesn't have any reviewers by default. So it's totally up to your team how you would like to handle them. If you want the merge conflict resolution to be reviewed, then you should go with option 2 where you open a new pull request on a branch with a…

@[deleted], yes there is. You can configure the merge strategies to only allow fast-forwards. However, depending on your configuration this might make it difficult to make sure your branch is always ahead of the destination and also give enough time for a green build (because rebasing will change the commit hashes, and…

Hi @AlfonsoP, Does your webhook contain a "changes" field as described in the documentation? A push event should contain the information around which ref changed, and what it changed from and to. It does not have information about the commits between the changes for a number of reasons, explained here. If you want the…

There is a feature request for this you can vote on and watch: https://jira.atlassian.com/browse/BSERV-4617

Maybe BSERV-4241?

Its not that there is broken code on master, but that the release branches should be strictly behind master. Master will contain the newest features, which you might not want merged into old release branches for the sake of compatibility.

Hi Rob, That makes more sense now, thanks. I made a mistake when I said that the release branches will eventually merge to master. It does for my team because our configuration is that master is the development branch and we have no 'production' branch. However, for your configuration that is not the case. I've checked the…

Hi @Rob Ormond, I'm a little bit confused because in one sentence you say you delete the release branch and then in the other sentence you say you want something to merge into the release branch. Do the release branches still exist or were they deleted? That aside, you cannot have master merge back upstream into your…