Confirmed users
502
edits
Buildduty/manifesto: Difference between revisions
Jump to navigation
Jump to search
updated manifesto to reflect ciduty support and newly defined escalation methods
m (Update BuildDuty to CiDuty. Renaming project) |
(updated manifesto to reflect ciduty support and newly defined escalation methods) |
||
| Line 3: | Line 3: | ||
CiDuty is an operational support team dedicated to monitoring and maintaining the health of Firefox’s continuous integration (CI) infrastructure. Employees are contractors located in Romania that provide 24/7 support. The team's '''''responsibilities include''''' but are not limited to: | CiDuty is an operational support team dedicated to monitoring and maintaining the health of Firefox’s continuous integration (CI) infrastructure. Employees are contractors located in Romania that provide 24/7 support. The team's '''''responsibilities include''''' but are not limited to: | ||
* [[ReleaseEngineering/Buildduty_manifesto#Firefox_CI_infrastructure_outage_coordination_and_investigation| Firefox CI infrastructure outage coordination and investigation]] | * [[ReleaseEngineering/Buildduty_manifesto#Firefox_CI_infrastructure_outage_coordination_and_investigation| Firefox CI infrastructure outage coordination and investigation]] | ||
* [[ReleaseEngineering/Buildduty_manifesto#Firefox_CI_support_and_case_management| Firefox CI support and case management]] | |||
* [[ReleaseEngineering/Buildduty_manifesto#Monitoring,_investigating,_and_debugging_issues_with_the_Linux,_Windows,_and_OS_X_Firefox_CI_infrastructure| Monitoring, investigating, and debugging issues with the Linux, Windows, and OS X Firefox CI infrastructure]] | * [[ReleaseEngineering/Buildduty_manifesto#Monitoring,_investigating,_and_debugging_issues_with_the_Linux,_Windows,_and_OS_X_Firefox_CI_infrastructure| Monitoring, investigating, and debugging issues with the Linux, Windows, and OS X Firefox CI infrastructure]] | ||
* [[ReleaseEngineering/Buildduty_manifesto#Monitoring_Firefox_CI_backlog/pending_counts| Monitoring Firefox CI backlog/pending counts]] | * [[ReleaseEngineering/Buildduty_manifesto#Monitoring_Firefox_CI_backlog/pending_counts| Monitoring Firefox CI backlog/pending counts]] | ||
| Line 10: | Line 11: | ||
* [[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]] | ||
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. | |||
== Things CiDuty can help with == | == Things CiDuty can help with == | ||
===== Firefox CI support and case management ===== | |||
First and foremost, ciduty are "case managers" to your CI developer needs. They have escalation paths and a well defined knowledge of the CI system as a whole. Given that, they are excellent at responding to issues and inquiries, and making sure anything Firefox CI related is triaged and managed appropriately. | |||
===== Firefox CI infrastructure outage coordination and investigation ===== | ===== Firefox CI infrastructure outage coordination and investigation ===== | ||
| Line 38: | Line 40: | ||
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. | ||
== Things | == Things ciduty are not responsible for == | ||
===== Firefox | ===== Fixing Firefox build and test tasks ===== | ||
While ciduty have the skills to diagnose CI infra health and make sure that the workers are in a good state, they are not knowledgeable about build and test internal logic. They do however know who owns what and can help you escalate to the appropriate team | |||