Branch specifics for relpro on beta

RESOLVED FIXED

Status

defect
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: rail, Assigned: rail)

Tracking

unspecified
Dependency tree / graph

Firefox Tracking Flags

(firefox47 fixed)

Details

Attachments

(2 attachments)

Apparently we are using nightly mozconfigs. Need a small tweak in testing/mozharness/configs/builds/branch_specifics.py
Attachment #8726950 - Flags: review?(jlund)
Posted patch l10n.diffSplinter Review
and l10n (ported from date)
Attachment #8726957 - Flags: review?(jlund)
Blocks: 1253756
Blocks: 1253757
Comment on attachment 8726950 [details] [diff] [review]
branch-specifics.diff

Review of attachment 8726950 [details] [diff] [review]:
-----------------------------------------------------------------

we are going to have to add 'beta' as the update_channel on monday. Once we do that, all CI jobs that are not 'promoted' will have that anyway right?
Attachment #8726950 - Flags: review?(jlund) → review+
Comment on attachment 8726957 [details] [diff] [review]
l10n.diff

Review of attachment 8726957 [details] [diff] [review]:
-----------------------------------------------------------------

exciting!

::: testing/mozharness/configs/single_locale/mozilla-beta.py
@@ +2,5 @@
> +    "nightly_build": True,
> +    "branch": "mozilla-beta",
> +    "en_us_binary_url": "http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-beta/",
> +    "update_channel": "beta",
> +    "latest_mar_dir": '/pub/mozilla.org/firefox/nightly/latest-mozilla-beta-l10n',

this was 'fake_kill_me' on date. OOC what happened on date when upload_env['LATEST_MAR_DIR'] was a non falsey value like that?

@@ +9,5 @@
> +    "hg_l10n_base": "https://hg.mozilla.org/releases/l10n/mozilla-beta",
> +
> +    # mar
> +    # No nightly on beta, using aurora mar tools
> +    "mar_tools_url": "http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/mar-tools/%(platform)s",

will this be on beta after uplift?
Attachment #8726957 - Flags: review?(jlund) → review+
(In reply to Jordan Lund (:jlund) from comment #3)
> Comment on attachment 8726950 [details] [diff] [review]
> branch-specifics.diff
> 
> Review of attachment 8726950 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> we are going to have to add 'beta' as the update_channel on monday. Once we
> do that, all CI jobs that are not 'promoted' will have that anyway right?

It's already "beta" in http://hg.mozilla.org/releases/mozilla-beta/file/tip/testing/mozharness/configs/builds/branch_specifics.py#l53, but not used unless it's either nightly (no nightlies on beta) or release_promotion (this patch). See MOZ_UPDATE_CHANNEL logic in https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/building/buildbase.py#832
(In reply to Jordan Lund (:jlund) from comment #4)
> exciting!

Can't wait!
 
> > +    "latest_mar_dir": '/pub/mozilla.org/firefox/nightly/latest-mozilla-beta-l10n',
> 
> this was 'fake_kill_me' on date. OOC what happened on date when
> upload_env['LATEST_MAR_DIR'] was a non falsey value like that?

AFAIK it's not used anywhere, but I don't want to add more risk now. It deserves a clean up in a different bug.

> > +    "mar_tools_url": "http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora/mar-tools/%(platform)s",
> 
> will this be on beta after uplift?

Yes and no. They will be generated, but they won't go into the latest directory (nightlies only). :( 

We should change the logic to use the martools, generated by en-US CI build. We already passing the prefix, so we can easily modify the script to use them. I'll file a separate bug.
https://hg.mozilla.org/mozilla-central/rev/d4bbcd3b6e7e
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.