Change Details

Various installs have requested Herald support for Harbormaster builds, particular build failures. This is reasonable, but if possible I'd like to identify the group of most common use cases and provide tailored tools for those use cases //before// providing Herald rules. Without this, installs may end up with a large number of complicated Herald rules when a simpler mechanism (like subscriptions) could replace most of them. --- **Use Cases** {icon chevron-right}{icon chevron-right}{icon chevron-right} From T10260: > I see this as being important for long running tests that should alert someone as soon as a failure is detected as I can't depend on all responsible parties to check the harbormaster application hourly. I think this is now moot, since build failures have alerted the most likely responsible users -- owners of related objects (commits and revisions) -- for a long time. --- - See also T13088.

Various installs have requested Herald support for Harbormaster builds, particular build failures. This is reasonable, but if possible I'd like to identify the group of most common use cases and provide tailored tools for those use cases //before// providing Herald rules. Without this, installs may end up with a large number of complicated Herald rules when a simpler mechanism (like subscriptions) could replace most of them. --- **Use Cases** {icon chevron-right}{icon chevron-right}{icon chevron-right} From T10260: > I see this as being important for long running tests that should alert someone as soon as a failure is detected as I can't depend on all responsible parties to check the harbormaster application hourly. I think this is now moot, since build failures have alerted the most likely responsible users -- owners of related objects (commits and revisions) -- for a long time. {icon chevron-right}{icon chevron-right}{icon chevron-right} From T5491: > At minimum I could use to this to notify IRC on a CI build failure This is an appropriate use case for Herald or Webhooks, and doesn't make sense as a standalone mechanism. --- - See also T13088.

Various installs have requested Herald support for Harbormaster builds, particular build failures. This is reasonable, but if possible I'd like to identify the group of most common use cases and provide tailored tools for those use cases //before// providing Herald rules. Without this, installs may end up with a large number of complicated Herald rules when a simpler mechanism (like subscriptions) could replace most of them. --- **Use Cases** {icon chevron-right}{icon chevron-right}{icon chevron-right} From T10260: > I see this as being important for long running tests that should alert someone as soon as a failure is detected as I can't depend on all responsible parties to check the harbormaster application hourly. I think this is now moot, since build failures have alerted the most likely responsible users -- owners of related objects (commits and revisions) -- for a long time. {icon chevron-right}{icon chevron-right}{icon chevron-right} From T5491: > At minimum I could use to this to notify IRC on a CI build failure This is an appropriate use case for Herald or Webhooks, and doesn't make sense as a standalone mechanism. --- - See also T13088.