Buildbot no longer supports Python 2.7 on the Buildbot master.
- class buildbot.reporters.BuildSetStatusGenerator
This report generator sends a message about builds in a buildset.
It is very similar to
BuildStatusGenerator but sends single message about all builds in a buildset, not individual builds.
The following parameters are supported:
Deprecated since Buildbot 3.5. Please use the
subjectargument of the
message_formatterpassed to the generator.
A string to be used as the subject line of the message.
%(builder)swill be replaced with the name of the builder which provoked the message.
%(result)swill be replaced with the name of the result of the build.
%(projectName)swill be replaced with the title of the Buildbot instance.
(list of strings or a string, optional). Defines the cases when a message should be sent. Only information about builds that matched the
modewill be included. There are two strings which can be used as shortcuts instead of the full lists.
The possible shortcuts are:
Send message for all cases. Equivalent to
('change', 'failing', 'passing', 'problem', 'warnings', 'exception').
If the argument is list of strings, it must be a combination of:
Include builds which were cancelled.
Include builds which change status.
Include builds which fail.
Include builds which succeed.
Include a build which failed when the previous build has passed.
Include builds which generate warnings.
Include builds which generate exceptions.
('failing', 'passing', 'warnings').
(list of strings, optional). A list of builder names to serve build status information for. Defaults to
None(all builds). Use either builders or tags, but not both.
(list of strings, optional). A list of tag names to serve build status information for. Defaults to
None(all tags). Use either builders or tags, but not both.
(list of strings, optional). A list of scheduler names to serve build status information for. Defaults to
(list of strings, optional). A list of branch names to serve build status information for. Defaults to
(boolean or a list of strings, optional). If
True, include all build logs as attachments to the messages. These can be quite large. This can also be set to a list of log names to send a subset of the logs. Defaults to
(boolean, optional). If
True, include the patch content if a patch was present. Patches are usually used on a
Tryserver. Defaults to
(optional, instance of
reporters.MessageFormatter) This is an optional instance of the
reporters.MessageFormatterclass that can be used to generate a custom message.