NOTE This bulletin has been superseded by Technical Bulletin 544
Effective February 23, access to the Enterprise (EN) Bitbucket server (https://mybitbucket.llnl.gov/dashboard) from the Collaborative Zone (CZ) will only be allowed via SSH git connections, and not via HTTPS. Going forward, in order to use the Enterprise Bitbucket, users will need to Enable SSH Access in their user profile in the Enterprise Bitbucket. Note, users are advised to secure your SSH private key with a passphrase to prevent unauthorized access to your repositories.
If you are already utilizing the “HTTPS” protocol for git communications from the CZ to the EN Bitbucket, you need only change the prefix of the URL from:
“https://<OUN>@mybitbucket.llnl.gov/scm/“ to “ssh://git@mybitbucket:7999/“
The following example demonstrates how to do this from the command line, followed by testing that it works with a “git pull":
$ git remote -v origin https://firstname.lastname@example.org/scm/cosmos/python-lora.git (fetch) origin https://email@example.com/scm/cosmos/python-lora.git (push) $ git remote set-url origin ssh://firstname.lastname@example.org:7999/cosmos/python-lora.git $ git remote -v origin ssh://git@mybitbucket:7999/cosmos/python-lora.git (fetch) origin ssh://git@mybitbucket:7999/cosmos/python-lora.git (push) $ git pull Already up-to-date.