Closed Bug 1426132 Opened 6 years ago Closed 6 years ago

set up birch for in-tree relpro RC testing


(Release Engineering :: Release Automation: Other, enhancement)

Not set


(firefox59 fixed)

Tracking Status
firefox59 --- fixed


(Reporter: bhearsum, Assigned: bhearsum)




(6 files, 2 obsolete files)

We're currently testing in-tree relpro for beta/devedition on maple, but we need to start testing it for RCs as well. Let's use birch for this!
Depends on: 1426138
Attached patch enable birch in buildbot (obsolete) — Splinter Review
This is the same as maple, minus devedition + s/beta/release/g.
Attachment #8937724 - Flags: review?(rail)
I realized while making a gecko patch that we'll need a unique tools repo (to avoid stomping on beta patcher/update verify configs) and unique mozharness configs (because the existing dev mozilla-release ones point at jamun, and we want to keep jamun working for buildbot staging releases).
Attachment #8937724 - Attachment is obsolete: true
Attachment #8937724 - Flags: review?(rail)
Attachment #8937728 - Flags: review?(rail)
Comment on attachment 8937729 [details] [diff] [review]
add mozharness configs for mozilla-release on birch

Review of attachment 8937729 [details] [diff] [review]:

LGTM. We'll verify the validity on birch :)
Attachment #8937729 - Flags: review?(rail) → review+
New in this version:
* Fixed release_channel_mappings
* Fixed typo in postrelease config name
* Get rid of accepted_mar_channel_id

I diffed mozilla-release vs. birch and couldn't find anything else of consequence.
Attachment #8937778 - Flags: review?(rail)
Attachment #8937728 - Attachment is obsolete: true
Attachment #8937728 - Flags: review?(rail)
Pushed by
set up birch for in-tree relpro testing. r=rail
Comment on attachment 8937778 [details] [diff] [review]
update buildbot-configs patch

Review of attachment 8937778 [details] [diff] [review]:

Attachment #8937778 - Flags: review?(rail) → review+
Closed: 6 years ago
Resolution: --- → FIXED
Attachment #8937778 - Flags: checked-in+
Depends on: 1426458
Re-opening this while waiting on the treeherder bits. Note to self: ping the Taskcluster team after that's done - they have some set-up to do, too.
Resolution: FIXED → ---
Attachment #8938476 - Flags: review?(catlee)
Attachment #8938476 - Flags: review?(catlee) → review+
Attachment #8938476 - Flags: checked-in+
I upgraded birch's scopes to allow it to do release signing. Specifically, I created a project:releng:nightly:level-3:birch role and granted it     project:releng:signing:cert:release-signing.

After that, I discovered chain of trust errors. I'm fixing those in
We can't bump pushapkscriptworker yet due to a bug in pushapkscript that jlorenzo is chasing down. The rest should be fine to bump, though.
Attachment #8939600 - Flags: review?(aki)
Comment on attachment 8939587 [details] [review]
allow birch to use release-signing in scriptworker

We can remove birch and maple when update verify can verify dep-signed builds :)
Attachment #8939587 - Flags: review?(aki) → review+
Attachment #8939600 - Flags: review?(aki) → review+
Attachment #8939600 - Flags: checked-in+
Attachment #8939644 - Flags: review?(aki) → review+
Attachment #8939644 - Flags: checked-in+
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.