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

RESOLVED WONTFIX

Status

P3
normal
RESOLVED WONTFIX
9 years ago
5 years ago

People

(Reporter: armenzg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [l10n])

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
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.
(Reporter)

Updated

9 years ago
Priority: -- → P3
Whiteboard: [l10n]
(Reporter)

Updated

9 years ago
Priority: P3 → P2
(Reporter)

Comment 1

9 years ago
Created attachment 397282 [details] [diff] [review]
enables 191 l10n builds to be uploaded to dated dir as well
Attachment #397282 - Flags: review?(ccooper)
(Reporter)

Comment 2

9 years ago
Modified topic since 192 is already doing it since we enabled l10n updates in it
Summary: 1.9.1 and 1.9.2 l10n repackages should upload to tbox-builds rather than latest → 1.9.1 l10n repackages should upload to tbox-builds rather than latest
(Reporter)

Comment 3

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

Comment 4

9 years ago
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.
Attachment #397282 - Flags: review?(ccooper)
(Reporter)

Updated

9 years ago
Depends on: 512300, 489313
(Reporter)

Updated

9 years ago
Priority: P2 → P3
(Reporter)

Comment 5

9 years ago
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.
(Reporter)

Updated

9 years ago
Assignee: armenzg → nobody
Component: Release Engineering → Release Engineering: Future
(Reporter)

Updated

9 years ago
OS: Mac OS X → All
Priority: P3 → --
Hardware: x86 → All
Mass move of bugs from Release Engineering:Future -> Release Engineering. See
http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Status: ASSIGNED → NEW
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
Summary: 1.9.1 l10n repackages should upload to tbox-builds rather than latest → 1.9.1 l10n repackages on-change should upload to tbox-builds rather than latest
(Reporter)

Comment 7

8 years ago
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.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.