jredmond Atlassian Team

The team itself doesn't really factor into repo permissions, except as a collection of groups and users. While the team owns the repos, access to each repo is still governed by the group and user settings within that repo's admin panel. You should be able to set up separate groups within the team: * one for internal devs *…

Both of those addresses are included in 104.192.136.0/21.

Have you recently restarted Postgres? If so, you'll need to tail the Postgres logs and watch for a message like "the system is ready to accept connections" before attempting to start Bitbucket. In the future, you can speed up Postgres reboots by issuing the checkpoint command (`psql -c checkpoint`) before stopping that…

You need to contact support.

The second URL includes the hash for a specific commit (ff45534a040217d687b68059e50e241b85b1766d); that URL will always show that specific commit. The first view, on the other hand, doesn't specify a commit, so it will show the head of the dev-clean branch (whatever that might be).

Are you asking about Bitbucket Server or Bitbucket Cloud?

I am not sure what you are asking here. Do you need to know where to find the address for your client? Are you trying to replace SSH addresses with HTTPS ones? Are you asking about Bitbucket Cloud (bitbucket.org) or Bitbucket Server (with some other address)?

Bitbucket Cloud or Bitbucket Server?

I don't see anything immediately wrong with what you've listed here, but Git has a couple environment variables that might help debugging: GIT_SSH_COMMAND="ssh -vv" GIT_TRACE=1 git fetch If you run that, does it indicate anything about where the process is failing?

Yes, there is - see https://confluence.atlassian.com/bitbucket/environment-variables-794502608.html

Yes, "Other" should work just fine for you. Those templates are meant to be starting points only; they do not represent the limit of what Pipelines can do.

Rsync is already incremental - it will only push (or pull) the difference between source and destination.

That article is for Bitbucket Cloud - have a look at https://docs.atlassian.com/bitbucket-server/rest/4.1.0/bitbucket-ssh-rest.html instead.

It looks like you're using Bitbucket Cloud, but the docs you quote here are for Bitbucket Server. For Bitbucket Cloud, the "privacy" option in that screenshot just needs to be unchecked.

You've tagged this as "Bitbucket" but this is not a Bitbucket question. That said, are you connecting through a proxy?

To clarify a little bit: you can connect to Bitbucket Cloud using HTTPS and SSH *through* a VPN tunnel, but you can't connect one end of your tunnel to Bitbucket Cloud.

Yes, that's the idea behind sites like Bitbucket Cloud (bitbucket.org) - you can each push and pull commits, and review content on the site.

I can't reproduce this - if I create a new repo in Bitbucket Cloud, and go to the "I have an existing project" section, then I get the SSH URL. Do you have an SSH key associated with your account?

Open the upstream repo, and select "Create fork" from the plus-sign menu on the left side.

Your only option here would be to set up an SSH key; associate it with a specific user account; and distribute the private key. I really do not like that option, though, because the act of sharing the private key is inherently insecure, and because you'll need to change the key every time your team membership changes. Far…

Bitbucket Cloud or Bitbucket Server?

Sorry, but this forum is for questions, answers, and discussion around Atlassian products. You may do better on a different forum.

The Premium plan allows you to prevent merges that have unresolved checks.

Those are two completely separate products, and many places only use one of them. If your organization uses Bitbucket Server, then you will need to talk to somebody in the organization to find out what the hostname is- that information does not exist on Bitbucket Cloud.

Public repos are read-only, except for any (registered) user you explicitly give write permissions. Anonymous users cannot push to any repo.

Can you be more specific about the kinds of problems you experience while pushing and pulling?

First, remove the key from that repository. Next, add the key to your own account - there's an option in your Bitbucket settings.

Fork that repository. In Bitbucket Cloud, open the repo and click the plus sign on the left. There should be a "create a fork" option. This will create a new repository in your account based on the upstream one.

I think you're confusing Bitbucket Cloud (hosted at bitbucket.org, no matter what the company) and Bitbucket Server (hosted at some other name, just not "*.bitbucket.org", "*.bitbucket.com", or "*.bitbucket.io"). They're different products, with similar but different APIs.

You're missing the static assets (images, CSS, JS, etc) that are typically available on our CDN (Cloudfront). Is there an issue with your access to cloudfront.net, or maybe a problem with the nearest cache?