616944 - builder.mozillalabs.com needs *something* to happen

Status: RESOLVED FIXED

(Mozilla Labs :: General, defect)

Description

[Dietrich Ayala (:dietrich)]

the old builder is broken, but live. perfect way to frustrate and anger developers.

we should redirect. however, then current developers can't get at their code.

ideally we should migrate everyone's code over. why was that not done?

at the very least we should:

1. put a HUGE note on every page saying that the old builder is turned off, with a link to the new one

2. disable the "test" button, since it's broken.

3. disable all editing buttons on the left hand side of the editor view.

Comment 1

[Zandr Milewski [:zandr]]

(In reply to comment #0)
> the old builder is broken, but live. perfect way to frustrate and anger
> developers.

Probably fixed now. We never fixed the /tmp bug on that machine.

> we should redirect. however, then current developers can't get at their code.
> 
> ideally we should migrate everyone's code over. why was that not done?

Nobody asked? Let me know what you need to migrate out of the labs VM. I assume it's a SQL dump and a tarball of the upload directory. Anything else?

I'd vote for migrating the uploaded code and then 301 to the production site.

Comment 2

[Dietrich Ayala (:dietrich)]

That sounds awesome Zandr, thanks. Should confirm that route with Daniel though.

Daniel, can you confirm if we want to do this?

If so, can you handle the communication end? Should email the jetpack list for sure, and a blog post would probably be good if you haven't already done that about the move to the new domain.

Comment 3

[Daniel Buchner [:dbuc]]

LOL as you guys were doing this I had filed an IT request to do a redirect. I guess we can disregard one or the other of these.

Comment 4

[Zandr Milewski [:zandr]]

Redirect is easy... what do you want to do with the old addons?

Comment 5

[Dietrich Ayala (:dietrich)]

We can't do a redirect until we have a migration, otherwise developers can't get to their addons on the old server.

Also, unless the migration can keep URLs intact and we do a fancy redirect that only redirects FQDN but not path, we might want to only redirect the old server's homepage, and allow direct links to addons to stick.

Comment 6

[Dietrich Ayala (:dietrich)]

Er, i meant that it keeps path in the request intact.

Comment 7

[Zandr Milewski [:zandr]]

(In reply to comment #5)
 
> Also, unless the migration can keep URLs intact and we do a fancy redirect that
> only redirects FQDN but not path, we might want to only redirect the old
> server's homepage, and allow direct links to addons to stick.

There are a couple of ways to do that, either with Rewrite rules or trafficscript on the Zeus. I'll probably do the latter, at least initially.

Comment 8

[Daniel Buchner [:dbuc]]

Well, I will have piotr do a patch to post a permanent notice on each page
saying that this domain's version has been deprecated. 0.7 was the last version
of the SDK that builder.mozlab ran, it is likely that a given user's add-ons
will need to be completely reworked, as the APIs are very different from 0.7 to
1.0b1.

Comment 9

[Zandr Milewski [:zandr]]

There is still a lot of activity on builder.mozillalabs.com, as evidenced by it filling up the disk periodically. Can we please retire this soon?

Comment 10

[Daniel Buchner [:dbuc]]

I am discussing a modal alert option with Piotr now. Either way this should be 301 redirected to the new builder.addons.mozilla.org domain by the close of January.

Comment 11

[Piotr Zalewa [:zalun]]

I guess best would be 
a) Modal window shown one time per user with an info (this site will vanish soon)
b) As we have the upload functionality (almost) ready, we may ask people to download their xpis and upload them on the new server.

Comment 12

[Daniel Buchner [:dbuc]]

Content for the modal:

We have recently moved the Add-on Builder to its permanent production home at http://builder.addons.mozilla.org. We will be shutting down this version at the end of January.

Migrating your existing add-ons to the new site:

1. Download your add-ons as xpi files via the "Download" button in the code edit view
2. Login to the new editor site and navigate to the My Account page
3. In the left column, you will find and option called "Upload Package", click it and enter the location of a add-on xpi you'd like to import.

This process should create a new add-on project on the Builder for each add-on xpi you upload.

Thank you for participating in this phase of the Add-on Builder's developer preview! We look forward to announcing the beta release of the Builder in the coming months.

Keep cranking out those add-ons!

Comment 13

[Piotr Zalewa [:zalun]]

Zandr - please update from branch update-1.0a6-with-modal

If you would also delete every /tmp/SDK* daily it should be fine

Comment 14

[Zandr Milewski [:zandr]]

would that patch apply to 1.0a5?

We never went to 1.0a6 in labs, because that migration was a lot of work.

Comment 15

[Zandr Milewski [:zandr]]

Need this to apply to a5, not a6. Upgrading to a6 is a lot of work for a "We've Moved" sign.

Comment 16

[Zandr Milewski [:zandr]]

resurrecting the corpse so dbuchner can edit again.

per dbuchner, update-1.0a5-with-initial-modal should work. Deploying now.

Comment 17

[Zandr Milewski [:zandr]]

...or I would if that branch existed.

Piotr: Got a branch/tag/changeset for me?

Comment 18

[Daniel Buchner [:dbuc]]

Piotr, where is the branch, I don't see it either.

Comment 19

[Daniel Buchner [:dbuc]]

This has been redirected for a while, closing this out as clean up.