I'm not sure how this issue has lived on this long, but, to our knowledge, there is no issue with this. If you are having issues using CNAMES with your account, please raise a support request to email@example.com and we will personally help you resolve it.
My apologies, but I do not understand what you are saying is missing on this particular feature. Are you looking for more/better documentation of how the CNAME static hosting functions? Or are you looking for repository level CNAME support (a different feature)?
@Marcus Bertrand Although I didn't make this issue but I think this issue means "Published website should be also working with CNAME". Now CNAME setting is only working with <username>.bitbucket.org, not CNAME setting.
Of course if Bitbucket supports repository level CNAME like Github Pages, nothing is better than it.
DISCLAIMER: I'm pissed off and I might start bitching.
I spent hours configuring that damn DNS that takes hours to propagate, and finally discovered that this damn thing doesn't work. The landing is finally on the Bitbucket page, NOT on the static website.
I know this is free and you get what you pay for. But could someone for once be clear and tell me : can I , or can I NOT use my custom domain aliasing directly the hosted static website? Because this is clearly not working.
I have a domain "mydomain.fr" OK
I have a static website "mydomain.bitbucket.org" working
I used CNAME to alias www.mydomain.fr to "mydomain.bitbucket.org." and that doesnt work
And, besides, there is nothing more annoying than documentation like this :
We still consider this an open feature request. However, we are now tracking it at https://bitbucket.org/site/master/issue/11257/support-custom-domains-cname-for-static. This is mostly to help disambiguate those users who were looking to direct a CNAME at their Repository (in the Bitbucket UI) or their Team/Account. We no longer support those configurations. If this is something you'd still like to see, please go vote on it!
It is now 2018. This issue may not have lots of votes, but I think that is mainly because most people won't bother voting. If their motivation for using bitbucket was to find a github pages alternative then when they find this issue and see that bitbucket pages do not support custom domains they will just leave. Bitbucket must have had it in mind that people would want custom domains when they created the bitbucket pages feature. I am perplexed as to how so many years could pass without having this feature implemented. I have read through this thread and am disappointed to see how poorly bitbucket communicated with their users on this issue. Now in 2018, with Microsoft's acquisition of github, there is an opportunity to gain more users. It is true that not every repo maintainer is interested in having a custom domain, but for those who are it is probably essential to them.