Will I need to seed the new key on my v6 self-hosted bitbucket runners? I don't currently seed the old one as far as I can tell. They are torn down each night.
Hi jeffp, welcome to the Community! For the clone itself you most likely don't need anything: the clone Pipelines runs at the start of each step goes over HTTPS, which this change doesn't touch. You can confirm it in the Build setup section of any step log, where the clone URL starts with https://x-token-auth:.
https://x-token-auth:
Where it does matter is any SSH operation inside your own scripts, such as pushing with $BITBUCKET_GIT_SSH_ORIGIN or submodules pointing at git@bitbucket.org:. Users in the announcement thread report that Pipelines has already switched that variable to ssh.bitbucket.org, and that the known_hosts Pipelines provides doesn't include the new hostname yet. Since your runners are rebuilt every night, I'd add the entry in the step script rather than on the host:
$BITBUCKET_GIT_SSH_ORIGIN
git@bitbucket.org:
ssh.bitbucket.org
curl -s https://bitbucket.org/site/ssh | sed 's/^bitbucket.org/ssh.bitbucket.org/' >> ~/.ssh/known_hosts
The host keys haven't changed, and Atlassian lists them in the announcement, along with the brownout schedule: SSH on bitbucket.org gets blocked in short windows from November 12 and is removed for good on December 10.
It looks like you're new here. Sign in or register to get started.