jredmond Atlassian Team

Could you please elaborate so that the next person having this problem knows what to do?

Sorry, but this is not a Jenkins forum.

Is your username "advancedarithmetic"?

Does the user or team named "advancedarithmetic" own that repo?

The Git submodule relationship is created in Git, not on a hosting platform. You'll need to run `git submodule add` with the submodule's URL, then commit and push.

Do you have branch restrictions enabled on the target branch?

The error message is pretty clear here - there's already a directory named "newfoil", and it isn't empty, so Git refuses to replace what's in there. You can either rename the existing "newfoil", or you can delete the existing "newfoil", or you can send the new clone to a different directory (`git clone…

The documentation you've linked is for Bitbucket Server, but you've tagged this for Bitbucket Cloud. (The image link says "access denied".) If you are looking for documentation for this for bitbucket.org, have a look at https://confluence.atlassian.com/bitbucket/branch-permissions-385912271.html instead.

What's the output of `git remote` in that repo? Does it still list an HTTPS URL?

Bitbucket Cloud is only available on the public Internet, so it can only send webhooks through the public Internet. You will need to modify your firewall. As for https://bitbucket-prlinks.us-east-1.prod.public.atl-paas.net/webhook/pr - that's the destination of that webhook, not the source. Don't call that from Jenkins.

This is not a problem that we can help you with here. Somebody who administers your repositories has configured them to be accessible only from certain IP addresses; your home address is not one of those addresses. Please ask your repo administrators.

If the Docker image you're using has zip built in, or if you install zip as part of the pipeline (perhaps with apt), then you can use zip in Bitbucket Pipelines.

403 implies that the application password you're using here doesn't have the correct access for that repository.

This is the answer I was coming here to post.

That's expected behavior - the "merge commit" strategy creates a new commit when you merge. If it's a problem, then one of the other strategies may be a better fit for you.

Please note that this is a bad idea, since you're now passing your credentials in plain text.

I'd actually suggest you remove that IP from your hosts file before going to that site/master issue. Bitbucket has not used that address in months.

There's no way around it - if you want to use SSH for two accounts from the same laptop, then you'll need to create a second key. However, you can skip the .SSH/config step by using your username in the remote URL (so "workuser@bitbucket.org" or "personaluser@bitbucket.org" instead of "git@bitbucket.org").

Do you have write permission to that repository?

Have you considered using an app password, as detailed in https://confluence.atlassian.com/bitbucket/two-step-verification-777023203.html#Two-stepverification-Troubleshootingtwo-stepverification ?

Git only tracks the executable bit and the file type in a file mode - it doesn't track ownership or the read or write bits, so those parts are left to the client to determine. You'll need to ask this in the Bamboo section.

The Bitbucket Server API (the second in your example, with `https://bitbucket.**.com/rest/api`) is built into the Bitbucket Server version you've installed. That API only changes when the BB Server version changes, and (unless you perform an upgrade on 12 April 2019) it will not change on 12 April 2019. For Bitbucket Cloud…

Check the status page: Repositories with a " . " (dot) in the repository name cannot be loaded through the website

Yes, Bitbucket Cloud is SOC2-compliant: https://www.atlassian.com/trust/compliance .

What version of LibreSSL? This looks like it's attempting to use an older version of TLS or SSL; since 1 December 2018 bitbucket.org has only supported TLS version 1.2 or higher.

That isn't an Atlassian address, so I can't give too much guidance. However, you should check your firewall or acl settings and confirm that that IP and port are permitted.

That IP is no longer valid. Please check your DNS and hosts file.

What are you trying to do?

The same issue with "Git basic", or something else?

Those are the inbound addresses - what Jenkins would use if it connects *to* Bitbucket. You need to whitelist the outbound addresses, since webhooks are connections *from* Bitbucket.