548605 - [tracking bug] release automation needs to support Linux x86_64 builds

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[[e-mail] (:bhearsum)]

We need to run through the automation with x86_64 release builds enabled and see what issues we hit, and fix them.

Comment 1

[Armen [:armenzg]]

I will try to give a stab at this next week. Time permitting.

Comment 2

[Armen [:armenzg]]

Attachment: WIP configs changes to run a linux 64 release on staging

Just posting for reference.

Comment 3

[Armen [:armenzg]]

In http://staging-stage.build.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.2-candidates/build3/
we can find the following:
* en-US.xpi
* linux-x86_64/en-US/
** namoroka-3.6.2.tar.bz2
** namoroka-3.6.2.txt (20100317140027 cd857b3b0e33)
* linux64_info.txt (buildID=20100317140027)
* update/linux-x86_64/en-US/
** namoroka-3.6.2.complete.mar

I will look into fixing the naming and try to trigger following builders.

Comment 4

[Armen [:armenzg]]

(In reply to comment #3)
> 
> I will look into fixing the naming and try to trigger following builders.

Modified these to the release mozconfigs:
 -ac_add_options --disable-tests
 -ac_add_options --with-branding=browser/branding/unofficial
 +ac_add_options --enable-tests
 +ac_add_options --enable-official-branding

Build in progress.

Comment 5

[Armen [:armenzg]]

That worked:
* http://staging-stage.build.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.2-candidates/build1/linux-x86_64/en-US/firefox-3.6.2.tar.bz2
* http://staging-stage.build.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.2-candidates/build1/linux-x86_64/en-US/firefox-3.6.2.tests.tar.bz2
* http://staging-stage.build.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.2-candidates/build1/linux-x86_64/en-US/firefox-3.6.2.txt
* http://staging-stage.build.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.2-candidates/build1/update/linux-x86_64/en-US/firefox-3.6.2.complete.mar

Comment 6

[Armen [:armenzg]]

Attachment: [WIP] enable Linux64 as another release platform

Comment 7

[Armen [:armenzg]]

Attachment: enable linux 64 for releases, l10n and some clean up (match staging and production)

Comment 8

[Armen [:armenzg]]

Attachment: allow linux64 L10n repackages

Comment 9

[[e-mail] (:bhearsum)]

Comment on attachment 438562 [details] [diff] [review]
allow linux64 L10n repackages

I really don't understand why we have this check at all, to be honest.

Comment 10

[[e-mail] (:bhearsum)]

Comment on attachment 438561 [details] [diff] [review]
enable linux 64 for releases, l10n and some clean up (match staging and production)

This patch is fine, but as you're probably aware, there's more work to be done before updates will work. Please do not update the production config until we know exactly which release we know which release we're shipping it with.

r+ for everything except the mozilla2/ release config.

Comment 11

[Armen [:armenzg]]

I won't have time for a while to deal with this putting into the pool.

For the record, we want to get this in with the alpha releases.

Comment 12

[Michael Kohler [:mkohler]]

This is a mass change. Every comment has "assigned-to-new" in it.

I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.

Comment 13

[Armen [:armenzg]]

Rail let me know if you need any help with this.
I was always able to get all the way to signing but never got around to know what to do with updates.
There is no much more work than updating the patches (few releases have already happened) and get it through past the updates generation. Ben has more knowledge on that area than me.

Comment 14

[Pavel Franc - Mozilla.cz]

Any news about linux64 L10n repackages ? It would surely help me with testing l10n on my linux64 box.

Comment 15

[Armen [:armenzg]]

(In reply to comment #14)
> Any news about linux64 L10n repackages ? It would surely help me with testing
> l10n on my linux64 box.

Hi Pavel,
Please use bug 571331 for tracking L10n nightly repackages.
We are able to do repackages for releases but for alpha releases we don't generate them.

Comment 16

[Rail Aliiev [:rail]]

All of the requested features of this bug have been fixed and tested in bug 559057. Closing.