Closed
Bug 1359237
Opened 7 years ago
Closed 7 years ago
document the process to enable a new branch for both taskcluster and buildbot builds
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kmoir, Assigned: spacurar)
Details
See bug 1353376, bug 1354284 for source material. Each time a new branch is added there are steps to add it to buildbot/taskcluster to ensure it is operational. This is not a common task so it is currently the steps are easy to forget. It would be great to have this all documented so we don't forget the steps in the future and can proceed more quickly.
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → spacurar
Reporter | ||
Comment 1•7 years ago
|
||
Looking at https://wiki.mozilla.org/ReleaseEngineering/How_To/Enable_a_branch_on_buildbot_and_taskcluster I think you need to include the part to enable the branch in treeherder from here https://bugzilla.mozilla.org/show_bug.cgi?id=1353376 https://github.com/mozilla/treeherder/pull/2415/commits/aec6bd11ebab4fd4a3a16f5e132fc1686fac8356 and enable the branch in taskcluster https://github.com/taskcluster/mozilla-taskcluster/pull/111/commits/3ebe051c1db2237d2a22506e387c1f5be6af3d19
Assignee | ||
Comment 2•7 years ago
|
||
I modified the wiki page with the requirements above. It looks like this: https://wiki.mozilla.org/ReleaseEngineering/How_To/Enable_a_branch_on_buildbot_and_taskcluster#Taskcluster_steps
Flags: needinfo?(kmoir)
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•