Confirmed users
502
edits
Buildduty/manifesto: Difference between revisions
Jump to navigation
Jump to search
adds changelog tracking to list of responsibilities
(updated manifesto to reflect ciduty support and newly defined escalation methods) |
(adds changelog tracking to list of responsibilities) |
||
| Line 4: | Line 4: | ||
* [[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#Firefox_CI_support_and_case_management| Firefox CI support and case management]] | ||
* [[ReleaseEngineering/Buildduty_manifesto#Track_Firefox_CI_infrastructure_changes| TrackFirefox CI infrastructure changes]] | |||
* [[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 13: | Line 14: | ||
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. | ||
== Things | == Things CIDuty can help with == | ||
===== Track Firefox CI infrastructure changes ===== | |||
CIDuty track and help publish all CI related changes. While this would be public, they can point people to this and help correlate regressions | |||
===== Firefox CI support and case management ===== | ===== Firefox CI support and case management ===== | ||