Open Bug 1906741 Opened 5 months ago Updated 5 months ago

Add Documentation on Best Practices Regarding Try / How to Identify a Good or Clear Try Run

Categories

(Fenix :: Tooling, task, P3)

Product:
Fenix
Component:
Tooling
Platform:
All
Android
Type:
task

Tracking

(Not tracked)

People

(Reporter: olivia, Unassigned)

References

(Blocks 1 open bug)

Details

Reading and interpreting try server Treeherder test runs is not intuitive. This bug is to add documentation on how to know when to rerun tests or how to identify intermittent failures on Treeherder.

This bug is to add docs to explain:

  • Intermittent Failures
    • Identification and how to prevent (link to this for prevention)
      • Identifying via existing listed intermittents
      • How to check Similar Jobs
  • What a "good" run should look like
  • How to rerun jobs
  • How to trigger jobs from Treeherder UI
  • Anything else that is not intuitive about Treeherder

Goal of docs is to:

  • Explain how to idenitfy a clear or good-to-go try push
  • Information on how to use Treeherder

(Not exactly a monorepo-enhancements, but I think it is in the same spirit of the meta and could help it get prioritized.)

Blocks: monorepo-enhancements
Severity: -- → S3
Priority: -- → P3
Summary: Add Documentation on Best Practices Regarding Try → Add Documentation on Best Practices Regarding Try / How to Identify a Good or Clear Try Run
See Also: → android-documentation
You need to log in before you can comment on or make changes to this bug.