CIDuty: Difference between revisions
Jump to navigation
Jump to search
m (→Team) |
m (Update BuildDuty to CiDuty. Renaming project) |
||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
= What is | = What is CiDuty? = | ||
CiDuty (formerly BuildDuty) is a team dedicated to helping out developers with Firefox continuous integration infra issues. We currently have six people based in Romania that provide 24/7 support. CiDuty complement the [[Sheriff|sheriffing team]] where sheriffs respond to Firefox code regressions, CiDuty respond to the infrastructure that builds and tests Firefox code. | |||
= Manifesto = | = Manifesto = | ||
The [[ReleaseEngineering/Buildduty_manifesto| | The [[ReleaseEngineering/Buildduty_manifesto| CiDuty manifesto]] describes the team responsibilities in a nutshell. | ||
= Team = | = Team = | ||
| Line 51: | Line 51: | ||
|} | |} | ||
= | = CiDuty priorities = | ||
The [[ReleaseEngineering/Buildduty_actionable| | The [[ReleaseEngineering/Buildduty_actionable| CiDuty actionable]] enumerates their daily/weekly sanity job. | ||
== Others == | == Others == | ||
There is a long list of '''[[ReleaseEngineering/Buildduty/Other_Duties|other, less-frequent duties]]''' that | There is a long list of '''[[ReleaseEngineering/Buildduty/Other_Duties|other, less-frequent duties]]''' that CiDuty can assist with. | ||
= Documentation = | = Documentation = | ||
There's a [https://wiki.mozilla.org/ReleaseEngineering/Buildduty/How_To wiki page] that aggregates useful info related to the tasks | There's a [https://wiki.mozilla.org/ReleaseEngineering/Buildduty/How_To wiki page] that aggregates useful info related to the tasks CiDuty is taking care of (as of December 2017). | ||
= Useful Links = | = Useful Links = | ||
| Line 65: | Line 65: | ||
* [https://secure.pub.build.mozilla.org/slavealloc/ui/#slaves Slave Alloc] | * [https://secure.pub.build.mozilla.org/slavealloc/ui/#slaves Slave Alloc] | ||
* [https://tools.taskcluster.net/provisioners Provision Explorer] | * [https://tools.taskcluster.net/provisioners Provision Explorer] | ||
* [https://secure.pub.build.mozilla.org/builddata/reports/slave_health/buildduty_report.html | * [https://secure.pub.build.mozilla.org/builddata/reports/slave_health/buildduty_report.html CiDuty Report] | ||
* [https://secure.pub.build.mozilla.org/buildapi/ Build Dashboard Main Page] | * [https://secure.pub.build.mozilla.org/buildapi/ Build Dashboard Main Page] | ||
** You can get JSON dumps for people to analyze by adding <code>&format=json</code> | ** You can get JSON dumps for people to analyze by adding <code>&format=json</code> | ||
Revision as of 08:48, 14 May 2018
What is CiDuty?
CiDuty (formerly BuildDuty) is a team dedicated to helping out developers with Firefox continuous integration infra issues. We currently have six people based in Romania that provide 24/7 support. CiDuty complement the sheriffing team where sheriffs respond to Firefox code regressions, CiDuty respond to the infrastructure that builds and tests Firefox code.
Manifesto
The CiDuty manifesto describes the team responsibilities in a nutshell.
Team
| Name | Profile | Social | Blog |
| Jordan Lund | jlund | github | blog |
| Zsolt Fay | zfay | github | N/A |
| Radu Iman | riman | github | N/A |
| Bogdan Crisan | bcrisan | github | N/A |
| Danut Labici | dlabici | github | N/A |
| Roland Mutter | rmutter | github | N/A |
| Adrian Pop | apop | github | N/A |
CiDuty priorities
The CiDuty actionable enumerates their daily/weekly sanity job.
Others
There is a long list of other, less-frequent duties that CiDuty can assist with.
Documentation
There's a wiki page that aggregates useful info related to the tasks CiDuty is taking care of (as of December 2017).
Useful Links
- Day 1 checklist
- Slave Health
- Slave Alloc
- Provision Explorer
- CiDuty 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(new)
- Old/Deprecated Public "How To" documents
- Private "How To" documents