At least some installs have been using Drydock in production for a while. This could be made easier -- and this task still has the best guide for it -- but I think nothing actionable here remains.

I'll call this out in the changelog, but behavior here is changing slightly (see T13258 and T11415):

The revision editor and diff editor should no longer be racing to edit the diff. The two revision editors may be racing now, but that race is significantly easier to resolve if it crops up.

This should work again now. The behavior probably needs refinement -- I don't remember exactly where we left it and I think there was some disagreement about who should or shouldn't receive build failure notifications before D10911 accidentally disabled this, but I think T9892 and other Harbormaster tasks discuss most of that.

File a bug report please.

It didn't work for me.

Here's what I'm thinking here:

• Add lint/unit/coverage "summary" field to each Build.
• Recalculate whenever new lint/unit objects show up (Possibly offline via daemon).
• arc-side lint/unit already generates a Build, so this one will hold the --nolint/--nounit information (+ excuse?)
• Anywhere we currently show that information, load the summary information and aggregate that, instead of aggregating all lints/units directly.

I don't think there's anything actionable remaining here that isn't covered elsewhere.

This should maybe also somehow interact with Artifact Files.

Aha! That makes sense, thanks for digging into it!

tl;dr: looks good!

Awesome, thanks!

I have a 500mb repo somewhere, and it would reproduce very easily to me, so I'll test this.

After D15427, this should be pretty clear for "Land Revision".

After D15424, arc fails when failing to push the staging area.

I've marked D15424 as fixing this, although I don't have a detailed understanding of exactly what goes on in the git protocol and which heuristics it is using. In particular, I haven't been able to trick it into doing too much work locally (maybe it also looks at parents?).

Drydock and Almanac are now available in the cluster. Here's a rough guide to configuring them -- I'll turn this into something formal once things work a little more smoothly.