Comments
-
The error message specifically mentions that it wants a password that has not been provided. If you were doing these fetches from the command line, then you would get a prompt, but VSTS has disabled prompts. Also, the URL listed there is HTTPS, so your SSH key is not relevant to this operation. You could use an SSH URL…
-
You should be able to set up a CNAME for bitbucket.org in any domain you manage, but it may be more trouble than it's worth. * It may cause a little bit of additional latency: the initial DNS lookup (for bitbucket.example.com) will trigger a second lookup (for bitbucket.org), and Bitbucket Cloud will then see the old host…
-
LFS isn't specifically determined by the size of the file, but instead by the naming pattern. It functions roughly like the .gitignore file - you could issue a command like `git lfs track "*.mp3"` to keep files with that naming pattern in LFS rather than in main repo storage.
-
Bitbucket Cloud already supports TLS1.3 (also ECDSA signing). I am not sure about the timeline for other products, though.
-
Also worth pointing out that Bitbucket SSH doesn't offer `OpenSSH_7.6p1 Ubuntu-4ubuntu0.3` as the remote version. You should also remove that ECDSA host key from your known_hosts file, as it is incorrect. (`ssh-keygen -R bitbucket.org` should take care of that.) Can you get anything from `ssh -Tvp443…
-
The key may also be in an unrecognized format, or it may be the wrong size (RSA keys must be at least 2048 bits; ECDSA must be 256, 384, or 521 bits; and DSA must be 1024 bits but don't use that because it's quite insecure).
-
Which part of Pipelines do you want them to be able to edit? The bitbucket-pipelines.yml file controls most of the active workflow, and it's a regular file within the repository - so any user with write access can modify it. They'd only need admin rights to change environment variables or SSH keys; to set up Pipes or other…
-
"curl 56" is a timeout receiving data (https://curl.haxx.se/libcurl/c/libcurl-errors.html lists the codes). Your client should allow you to set the buffer for HTTP-based connections, but the details of how to do that will depend on which client you're using (looks like maybe git bash?). You can also avoid cURL timeouts by…
-
You should actually be able to use SSH with the username, assuming the user has permissions and SSH keys set up appropriately. "git@bitbucket.org" still works, though, and it's a good generic choice for individual users (and the only option for access keys).
-
It looks like you've named the repo `https://brohb.bitbucket.io/` instead of just `brohb.bitbucket.io`. Can you rename it back to the shorter version, without the `https://` or trailing slash?
-
Which product named "Messenger"?
-
Is the time correct on the device running Authy?
-
Are you trying to make this work specifically with that version of Bitbucket Server (4.14.4)? Or are you attempting to work with Bitbucket Cloud (hosted at bitbucket.org)?
-
Does the security group on the Jenkins EC2 node permit outbound port-22 connections? Is Jenkins configured with a valid SSH key that's associated with either the repo in question or a user that has access to that repo?
-
Branch permissions! Users will still be able to edit on their local git repos - we have no control over what you do on your own systems - but you can configure branch permissions to disallow direct writes to one or more given branches. https://confluence.atlassian.com/bitbucket/branch-permissions-385912271.html has more…
-
This is not related to the original question. If your DNS resolution is broken, then changing git config parameters will not resolve that.
-
Do you have any sort of firewall or proxy between Jenkins and Bitbucket? Does Jenkins have a valid SSH key for this request? Is that key associated with an individual user with the appropriate level of access, or is that key set as an access key for the repo in question?
-
Hooks are not included in pushes or pulls, though, and users do not have direct filesystem access to the .git directory in a repo on Bitbucket Cloud.
-
You cannot use that IP with Pipelines. It is non-routable, and intended only for use in private networks (per RFC1918). You will need to give Pipelines a public IP address for that system.
-
There are no updates we can provide: this is something either in your network or in your ISP's network. (To put it another way: if bitbucket.org:22 were down, then I wouldn't have time to respond here because we'd be in the middle of a major incident.)
-
It's for CI/CD systems - using those keys, they can pull updates without occupying a user license.
-
Can you provide any more detail here?
-
A pre-receive hook won't do anything to prevent users from creating badly-named branches on their own systems. All it will do is prevent users from pushing those badly-named branches to your Bitbucket Server instance. If that's acceptable to you, then a pre-receive hook (or perhaps an update hook) should be plenty.…
-
Can you please provide some more information? An error message would be helpful - otherwise all we have to go on here is "there is a problem".
-
Is this for Bitbucket Server or Bitbucket Cloud?
-
This is not possible. Pipelines can't test any commits until it has them - and it doesn't get them until the push is complete.
-
You've added the public key to the repository as an access key. You need to remove it from the repo and add it to your account.
-
You're looking at Bitbucket Cloud (screenshot) but you've linked to Bitbucket Server documentation. Please see https://confluence.atlassian.com/bitbucket/branch-permissions-385912271.html instead.
-
This is a network issue, caused by one or more of the following: * Your computer is blocking connections to port 7999 * The destination system is blocking connections to port 7999 * Something in your network is preventing connections to port 7999 * You have the wrong address.
-
Pipelines uses the IPs from the "Valid IP addresses for Bitbucket Pipelines build environments" sections on https://confluence.atlassian.com/bitbucket/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall-343343385.html when it initiates the connection.