CIDuty: Difference between revisions
Jump to navigation
Jump to search
(Updated Buildduty general docs, added more useful links) |
(→Useful Links: added buildduty day 1 checklist) |
||
| Line 17: | Line 17: | ||
= Useful Links = | = Useful Links = | ||
* [[ReleaseEngineering/Buildduty/day_1_checklist|Day 1 checklist]] | |||
* [https://secure.pub.build.mozilla.org/builddata/reports/slave_health/ Slave Health] | * [https://secure.pub.build.mozilla.org/builddata/reports/slave_health/ Slave Health] | ||
* [https://tools.taskcluster.net/provisioners Provision Explorer] | * [https://tools.taskcluster.net/provisioners Provision Explorer] | ||
Revision as of 04:47, 30 January 2018
What is Buildduty?
Buildduty is a team dedicated to helping out developers with releng-related issues. We currently have two folks based in Romania that are available during their regular work hours. This is similar to the sheriff role that rotates through the sheriffing team . To avoid confusion, the releng sheriff position is known as "buildduty."
Manifesto
The buildduty manifesto describes the team responsibilities in a nutshell.
Buildduty priorities
The buildduty actionable enumerates their daily/weekly sanity job.
Others
There is a long list of other, less-frequent duties that buildduty can assist with.
Documentation
There's a wiki page that aggregates useful info related to the tasks Buildduty is taking care of (as of December 2017).
Useful Links
- Day 1 checklist
- Slave Health
- Provision Explorer
- Buildduty Report
- Build Dashboard Main Page
- You can get JSON dumps for people to analyze by adding
&format=json
- You can get JSON dumps for people to analyze by adding
- Public "How To" documents
- Private "How To" documents