CIDuty: Difference between revisions
Jump to navigation
Jump to search
m (→Team) |
(Moved 2 links.) |
||
| (9 intermediate revisions by 4 users not shown) | |||
| 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 and enquiries. 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. | |||
Have a question or issue with Firefox, build and test infrastructure? ciduty can help and ensure your inquiry gets answered. | |||
= Communication = | |||
As a 24/7 support team, ciduty are available via irc, email, and bugzilla. | |||
irc: | |||
* #ci - look for 'ciduty' in nick (monitors other channels as well) | |||
bugzilla: | |||
* needinfo or assign ciduty@mozilla.com | |||
* file under [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=CIDuty CIDuty] component if you are not sure where to file your CI related ticket | |||
email: | |||
* ciduty@mozilla.com | |||
= Manifesto = | = Manifesto = | ||
The [[ReleaseEngineering/Buildduty_manifesto| | The [[ReleaseEngineering/Buildduty_manifesto| CIDuty manifesto]] describes the team responsibilities in a nutshell. | ||
= Team = | = Team = | ||
| Line 51: | Line 67: | ||
|} | |} | ||
= | = CiDuty priorities = | ||
The [[ReleaseEngineering/Buildduty_actionable| | The [[ReleaseEngineering/Buildduty_actionable| CiDuty actionable]] enumerates their daily/weekly sanity job. | ||
= Documentation = | = Documentation = | ||
There's a [https://wiki.mozilla.org/ | There's a [https://wiki.mozilla.org/CIDuty/How_To HowTo wiki page] that aggregates useful info related to the tasks CiDuty is taking care of (as of January 2019). | ||
= Useful Links = | = Useful Links = | ||
* [[ReleaseEngineering/Buildduty/day_1_checklist|Day 1 checklist]] | * [[ReleaseEngineering/Buildduty/day_1_checklist|Day 1 checklist]] | ||
* [https://tools.taskcluster.net/provisioners Provision Explorer] | * [https://tools.taskcluster.net/provisioners Provision Explorer] | ||
* [https:// | * [https://wiki.mozilla.org/Buildduty/How_To Public "How To" documents] | ||
* [https:// | * [https://mana.mozilla.org/wiki/dosearchsite.action?queryString=title%3A%22How%20To%22&where=RelEng Private "How To" documents] | ||
= Deprecated / Archived = | |||
The following links and pages are out-of-date or not used anymore. They are still here for historical reasons. | |||
== Others == | |||
* '''[[CIDuty/Other_Duties|other, less-frequent duties]]''' that CiDuty can assist with. | |||
* [[ReleaseEngineering/How_To|Old/Deprecated Public "How To" documents]] | * [[ReleaseEngineering/How_To|Old/Deprecated Public "How To" documents]] | ||
= Meeting Notes = | == Meeting Notes == | ||
Old meeting docs from BuildDuty era. | |||
* [https://etherpad.mozilla.org/buildduty-notes Daily buildduty stand-up notes] | * [https://etherpad.mozilla.org/buildduty-notes Daily buildduty stand-up notes] | ||
* [[ReleaseEngineering/Buildduty/Meetings|Old buildduty weekly meetings notes]] | * [[ReleaseEngineering/Buildduty/Meetings|Old buildduty weekly meetings notes]] | ||
* [[ReleaseEngineering/Buildduty/SVMeetings| SoftVision buildduty stand-up notes]] | * [[ReleaseEngineering/Buildduty/SVMeetings| SoftVision buildduty stand-up notes]] | ||
Latest revision as of 15:09, 15 January 2019
What is CIDuty?
CiDuty (formerly BuildDuty) is a team dedicated to helping out developers with Firefox continuous integration infra issues and enquiries. 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.
Have a question or issue with Firefox, build and test infrastructure? ciduty can help and ensure your inquiry gets answered.
Communication
As a 24/7 support team, ciduty are available via irc, email, and bugzilla.
irc:
- #ci - look for 'ciduty' in nick (monitors other channels as well)
bugzilla:
- needinfo or assign ciduty@mozilla.com
- file under CIDuty component if you are not sure where to file your CI related ticket
email:
- ciduty@mozilla.com
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.
Documentation
There's a HowTo wiki page that aggregates useful info related to the tasks CiDuty is taking care of (as of January 2019).
Useful Links
Deprecated / Archived
The following links and pages are out-of-date or not used anymore. They are still here for historical reasons.
Others
- other, less-frequent duties that CiDuty can assist with.
- Old/Deprecated Public "How To" documents
Meeting Notes
Old meeting docs from BuildDuty era.