From cfc3ca1bbb9ac617006a5af575676eeb6e520390 Mon Sep 17 00:00:00 2001
From: Karen Arutyunov <karen@codesynthesis.com>
Date: Fri, 29 Sep 2023 14:05:33 +0300
Subject: Add support for *-build-*email package manifest value overrides in
 bdep-ci

---
 bdep/ci.cli | 25 ++++++++++++++++++-------
 1 file changed, 18 insertions(+), 7 deletions(-)

(limited to 'bdep/ci.cli')

diff --git a/bdep/ci.cli b/bdep/ci.cli
index c3f8825..5ffcd2f 100644
--- a/bdep/ci.cli
+++ b/bdep/ci.cli
@@ -87,15 +87,17 @@ namespace bdep
      builds build-{include,exclude}
      *-builds *-build-{include,exclude}
      *-build-config
+     *-build-email *-build-{warning,error}-email
      \
 
-     For the package configuration-specific build constraint overrides the
-     corresponding configuration must exist in the package manifest. In
-     contrast, the package configuration override (\cb{*-build-config}) adds a
-     new configuration if it doesn't exist and updates the arguments of the
-     existing configuration otherwise. In the former case, all the potential
-     build constraint overrides for such a newly added configuration must
-     follow the corresponding \cb{*-build-config} override.
+     For the package configuration-specific build constraint and email
+     overrides the corresponding configuration must exist in the package
+     manifest. In contrast, the package configuration override
+     (\cb{*-build-config}) adds a new configuration if it doesn't exist and
+     updates the arguments of the existing configuration otherwise. In the
+     former case, all the potential build constraint and email overrides for
+     such a newly added configuration must follow the corresponding
+     \cb{*-build-config} override.
 
      Note that the build constraints group values (both common and build
      package configuration-specific) are overridden hierarchically so that the
@@ -109,6 +111,15 @@ namespace bdep
      constraints are overridden, then for the remaining configurations the
      build constraints are reset to \cb{builds:\ none}.
 
+     Similar to the build constraints groups, the common and build package
+     configuration-specific build emails group value overrides are mutually
+     exclusive. If the common build emails are overridden, then all the
+     configuration-specific emails are removed. Otherwise, if any
+     configuration-specific emails are overridden, then for the remaining
+     configurations the build emails are reset to the empty values and the
+     build warning and error emails are removed (which effectively disables
+     email notifications for such configurations).
+
      If supported by the CI service, a package can be tested interactively
      in a specific build configuration using the \c{\b{--interactive}|\b{-i}}
      option. In this mode the CI service provides the login information for
-- 
cgit v1.1