1426132 - set up birch for in-tree relpro RC testing

Status: RESOLVED FIXED

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

Description

[[e-mail] (:bhearsum)]

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!

Comment 1

[[e-mail] (:bhearsum)]

Attachment: enable birch in buildbot

This is the same as maple, minus devedition + s/beta/release/g.

Comment 2

[[e-mail] (:bhearsum)]

Attachment: enable birch in my tools repo & separate configs

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).

Comment 3

[[e-mail] (:bhearsum)]

Attachment: add mozharness configs for mozilla-release on birch

Comment 4

[Rail Aliiev [: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 :)

Comment 5

[[e-mail] (:bhearsum)]

Attachment: update buildbot-configs patch

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.

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/18014f516e75
set up birch for in-tree relpro testing. r=rail

Comment 7

[Rail Aliiev [:rail]]

Comment on attachment 8937778 [details] [diff] [review]
update buildbot-configs patch

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

SHIPIT!

Comment 8

[Eliza Balazs [:ebalazs_]]

https://hg.mozilla.org/mozilla-central/rev/18014f516e75

Comment 9

[[e-mail] (:bhearsum)]

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.

Comment 10

[[e-mail] (:bhearsum)]

Attachment: add birch to bbb config

Comment 11

[[e-mail] (:bhearsum)]

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 https://github.com/mozilla-releng/scriptworker/pull/173

Comment 12

[[e-mail] (:bhearsum)]

Attachment: allow birch to use release-signing in scriptworker

Comment 13

[[e-mail] (:bhearsum)]

Attachment: bump most scriptworkers to 6.0.1

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.

Comment 14

[Aki Sasaki (not active)]

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 :)

Comment 15

[[e-mail] (:bhearsum)]

Attachment: allow birch in releaserunner3