Bitbucket custom domain CNAME record deprecation

Shocking news from Bitbucket service

We are writing to let you know that Bitbucket is discontinuing the Custom Domain feature (aka CNAME) as of July 1st, 2015. CNAMEs are used by relatively few accounts, and we are committed to building a better Bitbucket for all our customers by focusing our efforts on higher-impact features.
What does this mean for you? As a current CNAME user, your underlying Bitbucket account, kamtec1, will be unaffected. However, you will now need to access your account from the normal bitbucket.org URL instead of the custom domain, code.securityinet.com, you have been using. Existing custom domains will be removed and we will stop forwarding and accepting these CNAME records.
We’re sorry for any inconvenience this might cause you. If you want to learn more about the custom domain deprecation or changing your DNS records, please view the documentation page here.
Thanks,
Dennis Kromhout van der Meer
Bitbucket Product Manager

 

Why they  do it 🙁

 

Because we have stopped supporting CNAME’s by July 1, 2015 you must change your custom domain URL’s everywhere they are used to access your Bitbucket team, account, repositories, and any automated processes which access Bitbucket using the custom domain URL.

We’ve provided a set of examples to illustrate the process on this page.

Remove your custom domain

Before you remove your CNAME plan for changing the url references used to access the account and all it’s repositories as shown in the following examples.

To remove your CNAME

1. Do one of the following to access your team or account manage page: 
   1. For an individual account: Click Avatar> Manage account.
   2. For a team: Click Teams>your team name then click Manage team.
2. Click Custom domain.
3. Click Remove Custom Domain.

Your Bitbucket team, account, and associated repositories will no longer be accessible using the custom domain URL.

Change all URL’s to remove the custom domain

Change URL to access the account or team in Bitbucket

Removing the CNAME from your team or account will revert the URL used to access the team or account’s overview and management pages.

This URL to access account or team overview pages:

Will become:

Change the URL to access the repositories owned by the account or team

Removing the CNAME from your team or account will revert the URL used to access the team or account’s repositories.

This URL to access repositories:

Will become:

Change Git remote origin

If you used the CNAME domain when you initially set up your local repositories you will have to remove the remote origin entry for each repository and replace it so that it points to the repository in Bitbucket using: bitbucket.org/teamname/repo-name.

1. Check to see what your current remote is by switching to the directory containing your repository and using the git remote -vcommand. It should reveal your default fetch and push URL’s similar to the following:

   $ git remote -v origin    https://[email protected]/web-development.git (fetch) origin    https://[email protected]/web-development.git (push)

2. Remove the origin designation using git remote rm origin as shown in the following example:

   git remote rm origin

3. Add the path to your remote using git remote add origin as shown in the following example:

   git remote add origin    https://[email protected]/teamname/web-development.git

4. Verifiy the new remote using the  git remote -v command as shown in the following example:

   $ git remote -v origin    https://[email protected]/teamname/web-development.git (fetch) origin    https://[email protected]/teamname/web-development.git (push)

Change Git action URL’s

Git actions URL’s like this:

Will have to change to this:

Change mercurial action URL’s

Mercurial action URL’s like this:

Will have to change to this:

 

The information provided below is stored for archive purposes only.