1264272 - Add a `socorro` project

Status: RESOLVED FIXED

(Taskcluster :: Operations and Service Requests, task)

Description

[(not currently active) Ted Mielczarek]

Socorro uses Breakpad to build its stackwalker binary to process minidumps. We used to have a Jenkins CI to build the latest Breakpad and upload a tarball artifact, but that went away and now we just have the last tarball it produced in S3.

Setting up new Breakpad CI is tricky because it now lives in a Chromium git repo (mirrored to GitHub under the Google org), and I'd love to solve that eventually but not today. Today I would just like to have a script in the Socorro repo (bug 1230659) that we can run in Taskcluster to build a new Breakpad tarball.

I'd like to have this publish to a known route in the index so we can point the Socorro build at that route and have it build against the latest Breakpad build, and if we eventually get a CI job working it can publish there and we'd be back to using the latest Breakpad code automatically.

Dustin and I discussed this on IRC and he said that a `socorro` project sounded like the best fit here, and then anyone in that group would have the scopes to publish to `project.socorro.*` routes, so we could use like `project.socorro.breakpad.v1.builds.linux64.latest` as the route.

One thing I didn't have an answer for is that Dustin says that normally group membership is derived from LDAP groups, and I'm not sure that there's any sensible LDAP group that would map to Socorro developers/admins/whatever.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

Fixed!  I just added you as a project admin, but if there's a group, or others you'd like to add, we can do that too.

Comment 2

[(not currently active) Ted Mielczarek]

Ok, I'm not sure this is going to see much use outside of what I'm doing right now, but we can cross that bridge when needed. Thanks!