511460 - 1.9.1 l10n repackages on-change should upload to tbox-builds rather than latest

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect, P3)

Description

[Armen [:armenzg]]

Right now repackages on change for m-c are being pushed to tbox-builds/mozilla-central-l10n rather than nightly/latest-mozilla-central-l10n since we enabled nightly updates and dated dirs.

I would like that the repackages on change for the other two branches uploaded their repackages on change to tbox-builds in the same way even if we don't have updates in these two branches (1.9.2 will have them soon) to be consistent and don't cause confusion to localizers.

Comment 1

[Armen [:armenzg]]

Attachment: enables 191 l10n builds to be uploaded to dated dir as well

Comment 2

[Armen [:armenzg]]

Modified topic since 192 is already doing it since we enabled l10n updates in it

Comment 3

[Armen [:armenzg]]

BTW this has been tested on staging scenario for the nightly scenario since I wasn't sure if l10nDatedDirs could be enabled without l10nEnableUpdates.

Comment 4

[Armen [:armenzg]]

Comment on attachment 397282 [details] [diff] [review]
enables 191 l10n builds to be uploaded to dated dir as well

Good I just realized that I looked at the wrong log! As I was suspecting before doing the testing "buildid" was not being set since the target ident is not the same as in 192 and mc.

Comment 5

[Armen [:armenzg]]

Putting into the future list since I won't be able to look at it for at least the next 2 weeks. I will grab it if nobody does before I do.

Comment 6

[Chris Cooper [:coop] (he/him)]

Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.

Comment 7

[Armen [:armenzg]]

I don't see any value on spending time on this.

If you feel strongly that there is any value on this please let me know.