Confirmed users
67
edits
Buildduty/manifesto: Difference between revisions
m
Added info about PyUp work.
(adds changelog tracking to list of responsibilities) |
m (Added info about PyUp work.) |
||
| Line 11: | Line 11: | ||
* [[ReleaseEngineering/Buildduty_manifesto#Upload_new_packages_or_Python_modules_to_our_internal mirrors| Upload new packages or Python modules to our internal mirrors]] | * [[ReleaseEngineering/Buildduty_manifesto#Upload_new_packages_or_Python_modules_to_our_internal mirrors| Upload new packages or Python modules to our internal mirrors]] | ||
* [[ReleaseEngineering/Buildduty_manifesto#Routine_maintenance_of_the_Firefox_CI_configuration| Routine maintenance of the Firefox CI configuration]] | * [[ReleaseEngineering/Buildduty_manifesto#Routine_maintenance_of_the_Firefox_CI_configuration| Routine maintenance of the Firefox CI configuration]] | ||
* [[ReleaseEngineering/Buildduty_manifesto#PyUp_PR_work.| PyUp PR work]] | |||
The team’s responsibilities cover a wide variety of tasks, however they are not deeply knowledgeable about any particular tool, worker, or task running in our infra. Therefore, They should be treated as quick res ponders who are able to assess state in a timely manner, and escalate issues and inquiries to the appropriate person. | The team’s responsibilities cover a wide variety of tasks, however they are not deeply knowledgeable about any particular tool, worker, or task running in our infra. Therefore, They should be treated as quick res ponders who are able to assess state in a timely manner, and escalate issues and inquiries to the appropriate person. | ||
| Line 44: | Line 44: | ||
===== Routine maintenance of the Firefox CI configuration ===== | ===== Routine maintenance of the Firefox CI configuration ===== | ||
While most of the Taskcluster configuration is handled by the end-developer, we still have infrastructure using the Buildbot CI infrastructure as well. CiDuty has the knowledge and capability to modify the Firefox buildbot-configs and perform general maintenance of the Buildbot systems. Maintenance includes tasks such as retasking machines from one platform to another as capacity requirements demand, decommissioning machines, updating keys and secrets, etc. | While most of the Taskcluster configuration is handled by the end-developer, we still have infrastructure using the Buildbot CI infrastructure as well. CiDuty has the knowledge and capability to modify the Firefox buildbot-configs and perform general maintenance of the Buildbot systems. Maintenance includes tasks such as retasking machines from one platform to another as capacity requirements demand, decommissioning machines, updating keys and secrets, etc. | ||
===== PyUp PR work ===== | |||
CiDuty is in charge of keeping few repos, such as build-puppet, addonscript and treescript, always up-to-date with PRs that come from PyUp. In a general sense, they know how to investigate why tests are failing and know how to do the appropriate changes. | |||
== Things ciduty are not responsible for == | == Things ciduty are not responsible for == | ||