From 5ed5d2f98b604f4a59862757b0c2ec6f3f061d6c Mon Sep 17 00:00:00 2001 From: Karen Arutyunov Date: Fri, 29 Sep 2023 14:18:03 +0300 Subject: Document *-build-*email package manifest values in manual --- doc/manual.cli | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/doc/manual.cli b/doc/manual.cli index ded60d9..7cbed4a 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -1090,6 +1090,10 @@ license: [; ] [*-build-include]: [/] [; ] [*-build-exclude]: [/] [; ] +[*-build-email]: [; ] +[*-build-warning-email]: [; ] +[*-build-error-email]: [; ] + [build-file]: [bootstrap-build]: @@ -2343,6 +2347,10 @@ Note that the comment of the matching exclusion is used by the web interface [*-builds]: [; ] [*-build-include]: [/] [; ] [*-build-exclude]: [/] [; ] + +[*-build-email]: [; ] +[*-build-warning-email]: [; ] +[*-build-error-email]: [; ] \ The package build configurations where the substring matched by \c{*} in @@ -2427,6 +2435,33 @@ Note that the common build target configurations set is overridden hierarchically meaning that the \c{*-build-{include, exclude\}} overrides don't discard the common \c{builds} values. +The package build configuration can also override the common build +notification email addresses (specified with \l{#manifest-package-build-email +\c{build-email}}, \l{#manifest-package-warning-email \c{build-warning-email}}, +and \l{#manifest-package-error-email \c{build-error-email}}) by specifying the +matching \c{*-build-email} and/or \c{*-build-{warning, error\}-email} values. +For example: + +\ +bindist-build-config: +\\ ++bpkg.bindist.debian:--recursive=full ++bbot.bindist.upload: +; +Generate and upload binary distribution package. +\\ +bindist-build-error-email: builds@example.org +\ + +Note that to disable all the build notification emails for a specific package +build configuration the empty \c{*-build-email} value needs to be specified. +For example: + +\ +sys-build-config: ?sys:libz; Test with system dependencies. +sys-build-email: +\ + The default configuration should normally build the package with no configuration arguments and for the common target build configurations set. While not recommended, this can be overridden by using the special -- cgit v1.1