CI Automation: Difference between revisions

CI Automation (view source)

Revision as of 20:48, 15 May 2019

1,496 bytes added , 15 May 2019

big redesign

Jmaher

Confirmed users

3,376

edits

@@ Line 1: / Line 1: @@
 Welcome to the CI Automation team's landing page!
-We work on a wide range of projects around Mozilla's core [https://en.wikipedia.org/wiki/Continuous_integration continuous integration] (CI) pipeline. Some areas we focus on include:
+== Who we are ==
-* '''Performance''': developing perf harnesses and standing up new benchmarks/measurements
+We are a team of 9 engineers, 2 managers, 16 sheriffs (24x7 shift work in teams), and always a few interns, volunteers, and contractors.
-* '''Testing''': developing test harnesses and improving test stability
-* '''Data''': collecting CI related data, creating metrics and dashboarding
-* '''Configuration''': developing taskgraph and modifying which tasks run in CI
-* '''Tools''': developing the tools that Firefox core developers use to interact with CI
-* Plus many other projects
+Our team is split into 3 categories:
+* '''Integration''': integration of tests, platforms, configs into our CI system
+* '''Reporting''': dashboards and tools to view and work with data and the CI system
+* '''Sheriffing''': code sheriffing (not perf sheriffing) for mozilla-central based trees
+== Goal ==
+The CI Automation and Reporting teams are responsible for ensuring that we schedule appropriate tests, those tests produce useful results, we can view the results of the tests and collect data to make decisions, and finally that we are experts with the tools and provide sheriffing features for Firefox.
+== Mission ==
+To make the scheduling and reporting of our test results more accurate and easier to understand, leading to a yes/no answer from a try push.
+== Vision ==
+Our CI system schedules tests as efficiently as possible, highlights regressions as quick as possible, and our tools to monitor and manage what we schedule, what is run, and what was run is easy to use.
+== How we work ==
+We don't write automated tests for Firefox features, but we love to work with teams that have unique scenarios for automation or just questions.  We work closely with product development to ensure that our tests are run in the right environments and configurations, that developers know how to test their code and understand their results, and when code lands the sheriffs actively monitor the trees.
+Requests are done via Bugzilla or IRC chat (#cia, #treeherder, #sheriffs).  We prefer to have 2-3 weeks heads up on projects and more if possible.  Our work is 20% reactive where we help put out fires or treat a new issue as a P1, and 80% proactive where we plan work and get it done.
+== Integration: ==
+=== Routine work we do ===
+* new platforms
+** windows10/aarch64
+* new configs
+** fission
+* intermittents
+* test efficiencies
+=== Other work we do ===
+* capacity planning
+* test scheduling
+* new test environments
+** test-verify
+* harness support
 == Contact Us ==