The only remaining source code hosted on bzr.mozilla.org belongs to the Bugzilla Project, and a few sub-projects which are all Bugzilla-related. https://bzr.bugzilla.org/ now exists, and the git->bzr mirror from git.mozilla.org now mirrors to it rather than bzr.mozilla.org. The Bugzilla Project cannot host mozilla.org domain names for obvious reasons, but since people still use it to access bzr, we'd like to have it redirected. This will not help the bzr client using the bzr protocol as that will now reject or time out, but it will help people using http and https. Any URL hitting http://bzr.mozilla.org should redirect to http://bzr.bugzilla.org and https://bzr.mozilla.org should redirect to https://bzr.bugzilla.org (once bug 1155525 is fixed), keeping paths intact. The domain name bzr.mozilla.org probably needs to be hosted in the static cluster for this to happen. Thanks!
The redirect still blocks decom since the domain will stop working if they decom it before the redirect is in place.
Note that this bug is now ready to go when webops can get to it since the dependencies are all now resolved.
(In reply to Dave Miller [:justdave] (email@example.com) from comment #2) > Note that this bug is now ready to go when webops can get to it since the > dependencies are all now resolved. Do you need https://bzr.mozilla.org/ to redirect as well? Or just http?
Comment 0 says both http and https.
Note that all known bzr client do one of either 1) don't validate the certificate, or 2) support SNI, and most known browsers support SNI, so you should be able to use the existing cert from bzr2 on the vhost in the generic cluster (or wherever this ends up).
ETA was asked for on IRC, I'm hoping to get to this around the end of this week.
Our (dev services) plan was to put up a page up stating that bzr had been decommissioned and linking to the archive that we're going to post. I do like the idea of making the archive discoverable in this way and of being consistent in how we decommission our version control systems. (Plan is to use the same approach for CVS and, someday in the not too distant future, SVN.) Do you think redirecting to a page announcing bzr decommission and adding a link to that page to bzr.bugzilla.org will meet the needs of this bug?
Needinfo'ing Hal, since we've been talking offline about this very idea.
Decom in the near term is the plan. the old addr will stay live (but read only?) until the shutdown. ni :fubar to correct my inaccurate statements - he's driving the bzr decom
Flags: needinfo?(hwine) → needinfo?(klibby)
so much going in circles! I think we have two competing plans here, with justdave's original request and dev services'. justdave notes that hosting bzr.m.o elsewhere is a no-no, but I'm having difficulty in seeing how a redirect is actually any different. I dare say, it seems like it would be worse. Let's NOT redirect - we should make it clear that bzr.m.o is gone and that anyone still pulling should from there REALLY needs to catch up, while still providing information on what/how, and where to find the final tarball if needed.
I'm fine with that. We've broadcast the switchover on multiple Bugzilla channels, and we'll be putting it into release notes as well.
(In reply to Mark Côté [:mcote] from comment #12) > I'm fine with that. We've broadcast the switchover on multiple Bugzilla > channels, and we'll be putting it into release notes as well. So there's no action for us here except disable the DNS entry when you're good to go?
Okay I'm confused again--if we don't do a redirect (which is fine), are we going to host a static page saying that the system has been decommissioned? That's what I interpreted from comment 11, "while still providing information on what/how, and where to find the final tarball if needed". fubar, is that what you're saying?
yes, that is the plan
Are the SSH and BZR protocol services associated with bzr2.dmz.scl3 also retired? If I switch DNS for bzr.mozilla.org to point to a static page, those will then be inaccessible via that name. If that's ok, I've made the static page on our static cluster for bzr.mozilla.org and it looks like: $ curl -H 'Host: bzr.mozilla.org' http://static-non-ssl.zlb.phx.mozilla.net/ <html> <head><title>BZR has moved</title></head> <body> BZR has moved and is now found at <a href="https://bzr.bugzilla.org">bzr.bugzilla.org</a>. Please update your bookmarks to point to the new site. </body> </html> ~/bin$ Please let me know if that looks good and I'll switch DNS to it on Monday.
Yes, that's fine. All Bugzilla users (the only ones still potentially interested in bzr.m.o) have been instructed to use bzr.bugzilla.org. Just a nit: I haven't seen anyone use "BZR" in all caps like that... I would probably use "Bzr has moved".
(In reply to Eric Ziegenhorn :ericz from comment #16) > > Please let me know if that looks good and I'll switch DNS to it on Monday. Eric - we (dev services) are putting together a common landing page for all retired VCS systems (currently bzr & CVS). However, we can update the bzr.bugzilla.org landing page when that is done, so no problem with doing this cutover as soon as convenient.
bzr.mozilla.org is now simply the static page in comment 16, adjusted for case as requested. When you have a improved landing page just toss it my way and I can deploy that.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
bzr.mozilla.org nagios checks have been removed. Added a note to the Mana doc for bzr that the site has been replaced with a static page.
You need to log in before you can comment on or make changes to this bug.