Gary Atlassian Team

Hi @Philippe Abiven We have temporarily increased the size for specific repos that are near, or over the 2GB limit to unblock users while we are looking for a more suitable long term solution. We also adjusted when the warning messages trigger for these specific repos. Thank you, Gary

Hi @Lulu Sarnam, Currently, we only offer standard support for Bitbucket Cloud (including the premium license level) - listed under the Cloud deployment tab at https://confluence.atlassian.com/support/atlassian-support-offerings-193299636.html. We hope to expand the offerings in the future, but cannot currently share an…

@[deleted] apologies for that - it was picked up by our spam filter. Should re populate shortly. Gary

@Jerry Gardner (and anyone in the same situation)please feel free to open a support ticket at https://support.atlassian.com/contact/#/, and my team can help you with the limit on those repositories. Thank you, Gary Sackett Bitbucket Cloud Support Lead

Hey @Jan Hořický, We had an incident yesterday causing issues with invitations that I think might have caused this for you: https://bitbucket.status.atlassian.com/incidents/nyznqw7vcrj9 If you resend the invitations, I think you will be back in business. Let us know if that is not the case, and we will re engage. Cheers,…

Hi Everyone, This post aims to cover multiple scenarios with Sourcetree. There are a few things to unpack here: * There was a bug about a month ago with the GCM that is bundled with GIT for Windows:* https://github.com/Microsoft/Git-Credential-Manager-for-Windows/issues/802 * Bitbucket Cloud recently deprecated TLS 1.0 and…

Hi Joery, Simon's directions will work, but we also have a built in feature for this. Pipelines provides a way for you to store, and inspect, the fingerprint of a remote host, along with the host address. This allows you to visually verify that the public key presented by a remote host actually matches the identity of that…

Hi Lee, Could you please open a support issue at https://support.atlassian.com/, and our team will dig in to this for you. Cheers, Gary

@bonachea webhooks and notifications are 2 completely separate modules. You cannot create a webhook for wiki notifications. However, you can still configure notifications on a per repo basis that include changes to the wiki. These are configured on a per user basis, by the physical user -…

Hi Blake, There is nothing on the roadmap at the moment, so I went ahead and created a request for our Product team at https://bitbucket.org/site/master/issues/15194/allow-users-or-team-admins-the-ability-to. Cheers, Gary

Hi Everyone, Apologies for my delay in responding. We we shipped this a little later than anticipated, but as of this week you can now turn off the integration on a repo by repo basis. Once turned off, the icon will disappear from the repo. The direct url to turn off the integration:…

Hi Denis, Apologies, bad timing on my part. THe integration changed literally the day I posted my earlier reply. Currently, the main nav link will continue to display even if the integration is completely removed. We will have the integration updated in the next few weeks, so that the icon/link can be removed from the nav.…

@Simon you should be able to navigate to 'manage integrations' (https://bitbucket.org/account/user/user_or_team_name/addon-management) under your account/team, and remove the Trello integration. Cheers, Gary

Hi Fraser, I went ahead and created a support ticket for you at getsupport.atlassian.com since we will need to dig in to this, and do not want you to ahve to expose any company data. Cheers, Gary

Hi Sander, I usually load my key from the terminal using: ssh-add .ssh/"ssh_key_file" Cheers, Gary

Hey Tim, Sander, That issue is very specific to Pipelines, and was caused by an issue on the platform. Cheers, Gary

Hi Sander, This issue/post is very specific to Pipelines. For your issue, I would suggest creating a new question in the community, or creating a support ticket at getsupport.atlassian.com, and our support team will help you troubleshoot the issue. Cheers, Gary

Hi Sukhrob, It sounds like Windows is not saving your entry, which is why tou would continue to get the credential popup everytime you make a connection. There are a few different solutions that have been successful listed…

Hi Everyone, We've deployed a fix for this issue and will be continuing to investigate the root issue that caused it. Would you be able to provide us the url of the specific repo that you were having issues with? Please feel free to let us know if you encounter any further issues, or have any questions. Cheers, Bitbucket…

Hi TInus, By default, this is part of GIT, or HG. As long as you have GIT, or HG installed, then you just have to click Actions >> Open in terminal, and we will launch either the isntalled GIT terminal, or HG terminal. Cheers, Gary

Hi Sukhrob, Can you go to Control Panel -> Credential Manager -> Generic Credentials. Find any GIT, or HG entries, and remove them. Then re add a repo - you should then again get the pop up window >> add the proper creds. Can you confirm if you continue to get the popup after that? Cheers, Gary

Hi Brian, Can you run the following from your terminal, and let us know if your SSH key is loaded: ssh-add -l Cheers, Gary

Hi Sander, Can you run the following from your terminal, and let us know if your SSH key is loaded: ssh-add -l Cheers, Gary

You can also try the new beta release (SourceTree 2.1.0) that should fix this issue: https://downloads.atlassian.com/software/sourcetree/windows/beta/SourceTreeSetup-2.1.0-beta-002.exe Release notes can be viewed at https://www.sourcetreeapp.com/update/windows/beta/ReleaseNotes_2.1.0-beta-002.html. Cheers, Gary

Hey Scott, Upgrading is the preferred path. Alternatively, you can uncheck the option "Use this version of SourceTree for UIR Association" in the Tools/Options/General Tab and remove the following registry key "HKEY_CURRENT_USER\SOFTWARE\Classes\sourcetree\shell\opencommand" - this disables the handling of the…

Hi Dan, Which version of OSX are you using? 2.5.1 only supports OSX 10.11, or later. Cheers, Gary

Hi Scott, Please see https://confluence.atlassian.com/display/SOURCETREEKB/SourceTree+Security+Advisory+2017-05-10 & https://nvd.nist.gov/vuln/detail/CVE-2017-8768 for more information. Can you also tell me if you are using the Windows version, or OSX version of SourceTree? Cheers, Gary

Hi Penny, Unfortunately, the only way is to upgrade to the latest version of SourceTree. The latest versions only support OSX 10.11 or later. Without upgrading, you run the risk of actively keeping your system open to this issue. Cheers, Gary

Hi Lindsey, Which version of OSX are you using? 2.5.1 only supports OSX 10.11, or later. Cheers, Gary

Hi Matt, It may be that your teamate has not enabled Pipelines for those specific repos - can you ask them to go to the Pipelines tab, and then click the enable button on the main screen. Once Pipelines is enabled, you should be able to access builds as long as you have write access to the repo. Build minutes are…