add branch specific configs for mozharness ci builds

RESOLVED FIXED

Status

Release Engineering
Applications: MozharnessCore
RESOLVED FIXED
2 years ago
9 months ago

People

(Reporter: jlund, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
this will be required once gecko 46 makes it to esr. I suppose that's esr52?
(Reporter)

Comment 1

2 years ago
we will need something like https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/builds/branch_specifics.py#40 but for esr branch..
Hm, I assume you mean Firefox 45.0 and not 46.0? :) The branch which will be created will be mozilla-esr45.
(Reporter)

Comment 3

2 years ago
(In reply to Henrik Skupin (:whimboo) from comment #2)
> Hm, I assume you mean Firefox 45.0 and not 46.0? :) The branch which will be
> created will be mozilla-esr45.

I still think we depend on gecko 46. Basically m-b,m-r,esr based repos use buildbot only to build desktop ff. But starting beta 46 (next week), we are switching to mozharness to build and that will be riding the trains.

So, once 46 makes it to m-r, that will use mozharness and so on. iiuc, esr will won't build with mozharness until we either force it or a build based on 46 or higher is on it. Which I suppose will never be esr45, but will be on esr52.

Are we on the same page?
Oh, now its clear to me. Thanks for clarifying. That all sounds great.

Updated

9 months ago
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.