673089 - Automate Lightning Beta Releases

Status: RESOLVED FIXED

(Calendar :: Build Config, defect)

Description

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

The release automation used for applications doesn't really work well for Lightning, there are too many special cases. It might be better to create special automation using extensionfactory.py that takes Lightnings special cases into account.

Comment 1

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

Using this bug as a meta-bug to track things needed to create automated beta builds. Please see dependent bugs.

Comment 2

[Worcester12345]

Fixing https://bugzilla.mozilla.org/show_bug.cgi?id=401779  would eliminate the need for these separate "automation" and "updating" processes.

Comment 3

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

(In reply to Worcester12345 from comment #2)
> Fixing https://bugzilla.mozilla.org/show_bug.cgi?id=401779  would eliminate
> the need for these separate "automation" and "updating" processes.

But it wouldn't fix the "missing-strong-module-owner-for-each-area" problem.

Comment 4

[Worcester12345]

Any chances of finalizing this bug?

Comment 5

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

Sure thing! I don't think we have to do anything here anymore. The build process is handled by Thunderbird and all thats left is bug 656350 which is just an enhancement to what I am doing now.

Comment 6

[Worcester12345]

(In reply to Philipp Kewisch [:Fallen] from comment #5)
> Sure thing! I don't think we have to do anything here anymore. The build
> process is handled by Thunderbird and all thats left is bug 656350 which is
> just an enhancement to what I am doing now.

Thanks. Do you have a link to the code that was fixed here? I think it is called a differential.
?

Comment 7

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

The code is in the various dependencies for this bug