Page MenuHomePhabricator

Don't run Herald build and mail rules when they don't make sense
ClosedPublic

Authored by epriestley on Oct 24 2017, 9:21 PM.
Tags
None
Referenced Files
F13047644: D18731.id44961.diff
Thu, Apr 18, 2:01 PM
Unknown Object (File)
Wed, Apr 17, 3:16 PM
Unknown Object (File)
Mon, Apr 15, 2:45 PM
Unknown Object (File)
Thu, Apr 11, 7:24 AM
Unknown Object (File)
Tue, Apr 9, 5:31 PM
Unknown Object (File)
Fri, Apr 5, 5:21 PM
Unknown Object (File)
Sat, Mar 30, 5:19 AM
Unknown Object (File)
Thu, Mar 28, 6:36 PM
Subscribers
Restricted Owners Package

Details

Summary

Ref T2543. Fixes T10109.

Currently, Herald only runs in Differential when a change updates the diff. This is partly for historical reasons, and partly because we don't want to restart builds every time someone makes a comment. However, this behavior is inconsistent with other applications (which always trigger on any change), and occasionally confusing to users (in T10109, for example) or otherwise undesirable.

A similar issue is that T2543 has introduced a "Draft" state, where revisions don't send normal mail until builds finish. This interacts poorly with "Send me an email" rules (which shouldn't do anything here) and particularly with "Send me an email + only run these actions the first time the rule matches", since that might have an effect like "do nothing when the revision is created, then never anything again since you already did nothing once".

To navigate both of these issues, let objects tell Herald that certain actions (like mail or builds) are currently forbidden. If a rule uses a field or action which is currently forbidden, the whole rule automatically fails before it executes, but doesn't count toward "only the first time" as far as Herald's tracking of rule execution is concerned.

Then, forbid mail for draft revisions, and forbid builds for revisions which didn't just get updated. Forbidding mail fixes the issues with "Send me an email" that were created by the introduction of the draft state.

Finally, make Herald run on every revision update, not just substantive updates to the diff. This resolves T10109.

Test Plan

Created revisions via the draft -> submit workflow, saw different transcripts. Here's a mail action being forbidden for a draft:

Screen Shot 2017-10-24 at 2.09.46 PM.png (148×616 px, 25 KB)

Here's a build action being forbidden for a "mundane" update:

Screen Shot 2017-10-24 at 2.10.19 PM.png (152×768 px, 28 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable