run_976254d97b27dc01

input

{
  "request": "Triage Jira ticket SREIN-1668: Need new sub-domain name + public bucket to host statistics about review latency for Firefox",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/SREIN-1668"
  ],
  "sourceContext": {
    "issue": "SREIN-1668"
  }
}

summary

SREIN-1668 requests a new Mozilla-hosted subdomain (suggested: tests.firefox.dev) and a public hosting solution (suggested: Netlify with deploy previews) to serve Firefox review-latency statistics dashboards, currently hosted on GitHub Pages by the Engineering Effectiveness team. The ticket is in Backlog with no comments, no assignee noted, and no explicit deadline, though the requester notes urgency in getting a stable URL so engineers can be pointed to it. No Confluence runbook/design doc was linked in the description (the referenced URLs appear to have been stripped out), so no additional design context could be retrieved. This looks like a standard infra provisioning request (DNS delegation + static site hosting) that SRE-in should be able to scope with a few clarifying questions before actioning.

findings

• none

proposed actions

Thanks for the request! To move this forward, could you confirm a few details:

1. Subdomain: Is `tests.firefox.dev` the final preferred name, or should we consider alternatives (e.g. something under `mozilla.dev`/`mozilla-eng.dev`)? Please confirm the exact DNS record needed (CNAME/ALIAS target) once hosting is chosen.
2. Hosting: You mentioned Netlify as a possible option — is there a preference for Netlify vs. an S3+CloudFront static bucket (which is more common for other Mozilla public dashboards)? Either is feasible; the choice affects how we wire up deploys.
3. Deploy trigger: Since the dashboard's data files will soon be generated by a Taskcluster job (patch pending review), can you link that patch/task definition? We'll want the hosting setup to support a deploy hook triggered from that Taskcluster job (e.g., webhook build trigger for Netlify, or S3 sync step at the end of the TC task) rather than relying on manual pushes.
4. Repo: Could you share the GitHub repo currently backing the GitHub Pages site, so we can set up the build/deploy pipeline?

Once we have these details we can scope the DNS delegation and hosting bucket/site creation. No blocking dependencies seen so far; will move to grooming once the above is confirmed.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "SREIN-1668"
    },
    "result": {
      "key": "SREIN-1668",
      "summary": "Need new sub-domain name + public bucket to host statistics about review latency for Firefox",
      "status": "Backlog",
      "description_text": "(currently hosted on github pages at    ) would benefit from being hosted on Mozilla infrastructure (that can probably be netlify, with deploy previews). It would also be nice to have a more official sounding domain name pointing to it. tests.firefox.dev would be nice. The data files backing these dashboards should soon be automatically generated by taskcluster (there\u2019s a patch up for review in    )  Team:  Engineering Effectiveness No deadline, but the sooner we have a stable url, the sooner we can start pointing engineers to these dashboards.",
      "comment_count": 0,
      "comments": []
    }
  }
]

log