Switch comm-1.9.1 builds to aus2.mozillamessaging.com

RESOLVED FIXED in Thunderbird 3.0b3

Status

RESOLVED FIXED
10 years ago
9 years ago

People

(Reporter: gozer, Assigned: gozer)

Tracking

other
Thunderbird 3.0b3
x86
Linux
Dependency tree / graph
Bug Flags:
blocking-thunderbird3 +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [pref changed][buildbot config changes on Thur 16th])

Attachments

(1 attachment)

(Assignee)

Description

10 years ago
Before we can move the remaining 2 build VMs still hosted at MoCo, we need to switch them over to using the MoMo AUS server.
(Assignee)

Comment 1

10 years ago
Created attachment 371897 [details] [diff] [review]
pref patch to switch to aus2.mozillamessaging.com
(Assignee)

Comment 2

10 years ago
Before that patch can land, this will also need buildbot config changes to send the aus snippets elsewhere.
(Assignee)

Updated

10 years ago
Blocks: 487208
Have we got aus2.mozillamessaging.com set up to the same (or similar) methods that MoCo use to get their stats? (e.g. number of nightly users based on pings)

IMHO we should be able to track these before we do the switch - otherwise we're likely to loose that data.
(Assignee)

Comment 4

10 years ago
(In reply to comment #3)
> Have we got aus2.mozillamessaging.com set up to the same (or similar) methods
> that MoCo use to get their stats? (e.g. number of nightly users based on pings)

Not at all, all that stuff on their end is prety fancy Pentaho stuff we definitely don't have.

> IMHO we should be able to track these before we do the switch - otherwise we're
> likely to loose that data.

I do archive all log date, forever, so the data wouldn't be lost, just much harder to inspect. We definitely need some sort of plan/idea for that kind of data analytics, but it's an area where I am relatively clueless.

Probably a good idea to talk to the folks @ MoCo behind this.
(Assignee)

Comment 5

9 years ago
http://hg.mozilla.org/build/buildbot-configs/rev/de69b8b4c941

Aditionnal configuration to send comm-1.9.1 nightly update snippets to our own AUS server as well. This will allow for testing our AUS server while keeping updates being served out of the mozilla AUS server.
(Assignee)

Updated

9 years ago
Depends on: 501201
(Assignee)

Updated

9 years ago
Blocks: 500676
(Assignee)

Comment 6

9 years ago
I've manually sucked out the comm-1.9.1 nightly AUS snippets from MoCo's AUS server and pushed them out to our AUS server, so it's ready for testing.
Comment on attachment 371897 [details] [diff] [review]
pref patch to switch to aus2.mozillamessaging.com

r=Standard8 for when we're ready to land this.
Attachment #371897 - Flags: review+

Updated

9 years ago
Whiteboard: [tb3needs]
As already mentioned elsewhere, needed for b3 to allow us to fully test update from MoMo's AUS at b4.
Assignee: nobody → gozer
Flags: blocking-thunderbird3+
Whiteboard: [tb3needs] → [ready to land on Wed 15th]
Target Milestone: --- → Thunderbird 3.0b3

Comment 9

9 years ago
(In reply to comment #6)
> I've manually sucked out the comm-1.9.1 nightly AUS snippets from MoCo's AUS
> server and pushed them out to our AUS server, so it's ready for testing.

Are the snippets automatically updated nightly yet.
I use the "help>>check for update " option, and rarely go a day without updating.

Comment 10

9 years ago
(In reply to comment #9)
> (In reply to comment #6)
> > I've manually sucked out the comm-1.9.1 nightly AUS snippets from MoCo's AUS
> > server and pushed them out to our AUS server, so it's ready for testing.
> 
> Are the snippets automatically updated nightly yet.
> I use the "help>>check for update " option, and rarely go a day without
> updating.

Seems all is well, as setting app.update.url to
https://aus2.mozillamessaging.com/update/3/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
Updated from 20090713 to 20090714 successfully here.
(In reply to comment #9)
> (In reply to comment #6)
> > I've manually sucked out the comm-1.9.1 nightly AUS snippets from MoCo's AUS
> > server and pushed them out to our AUS server, so it's ready for testing.
> 
> Are the snippets automatically updated nightly yet.
> I use the "help>>check for update " option, and rarely go a day without
> updating.

Currently they are manually copied over. We'll be landing the preference patch after today's (Wednesday) nightlies, Thursday's nightlies will be served from the old server, Friday's nightlies will use MoMo's server.

In between the Thursday and Friday nightlies we'll be changing the config so that we're automatically pushing the updates to the MoMo server.
Checked in: http://hg.mozilla.org/comm-central/rev/6e2787312bd8

This will be picked up in tomorrow's builds (and the B3 builds) and then we'll switch the builders to post to aus2.momo tomorrow and it will be used for Friday's updates.
Whiteboard: [ready to land on Wed 15th] → [pref changed][buildbot config changes on Thur 16th]
(Assignee)

Comment 13

9 years ago
(In reply to comment #12)
> Checked in: http://hg.mozilla.org/comm-central/rev/6e2787312bd8
> 
> This will be picked up in tomorrow's builds (and the B3 builds) and then we'll
> switch the builders to post to aus2.momo tomorrow

Actually, what we'll do instead is close bug 460094 and move the builders from MoCo to MoMo hosts. Same end-result, different way around.

> and it will be used for Friday's updates.

Correct!
(Assignee)

Comment 14

9 years ago
Switchover complete. Folks still holding onto a build from before the switch will see 2 updates in a row next time they check for update. One will update them to the latest build that was published on aus2.mozilla.org, then one more to the latest comm-1.9.1 build.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.