Mattermost status reporter for Buildbot
Install:
pip install buildbot-mattermost-reporter
Usage example in Buildbot master.cfg:
from buildbot.plugins import reporters
c['services'].append(
reporters.MattermostStatusPush(
webhook_url="https://mattermost.example.com/hooks/hookidstring",
),
)
Parameters to MattermostStatusPush:
MattermostStatusPush(
webhook_url, channel=None, icon_url=None, icon_emoji=None,
timezone=None, username_fn=None, buildstatusgenerator_kwargs=None,
generators=None,
**kwargs)
webhook_url(string): Mattermost Webhook URL given when webhook is createdchannel(string): See Mattermost incoming webhooks docsicon_url(string): See Mattermost incoming webhooks docsicon_emoji(string): See Mattermost incoming webhooks docstimezone(datetime.tzinfo): Convert timestamps in messages to a timezone, if set. Otherwise timestamps are UTC. Concretetzinfoobjects could be created with dateutil, which Buildbot has as dependency.username_fn(callable): Callable that takes a string argument, which is one of the individuals in the builds owners property, and returns a Mattermost username. The username is used for failing builds, where the message includes a line like@owner1, @owner2, .... By default a function is used that assumes that each owner is an e-mail address and returns the part before @, i.e.user@example.comreturnsuser. An example where failing builds would notify the whole channel instead would beusername_fn=lambda _: "channel".buildstatusgenerator_kwargs(dict): Any extra keyword arguments toreporters.BuildStatusGenerator, e.g.buildstatusgenerator_kwargs={'report_new': True}.generators(list): To override generator created byMattermostStatusPushand format Mattermost messages in a custom manner.**kwargs: Any extra arguments toreporters.HttpStatusPush.
Metadata
Release files for buildbot-mattermost-reporter 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| buildbot-mattermost-reporter-0.2.0.tar.gz | 8.3 kB | Without provenance | Details for buildbot-mattermost-reporter-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| buildbot_mattermost_reporter-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for buildbot_mattermost_reporter-0.2.0-py3-none-any.whl |
Total release size: 14.3 kB
Release files / buildbot-mattermost-reporter-0.2.0.tar.gz
| Download URL | buildbot-mattermost-reporter-0.2.0.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa41a7f9c9b1e62593961ef42df5f912cf9c362237163ed65204f0623d05990c
|
|
BLAKE2b-256 checksum How to use checksums |
0b49949344265714aa5d1fc7b989b4c5fd5e8b536504784437e7e73bdb3aa457
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.6
|
Release files / buildbot_mattermost_reporter-0.2.0-py3-none-any.whl
| Download URL | buildbot_mattermost_reporter-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c434625793e11ef2af56c91a6a3a114e23c3d7926a71b96ccb0249ed274810b
|
|
BLAKE2b-256 checksum How to use checksums |
81083f4e31b5d21a8c4b823651bd602652e4d5823a11c5b9bcd510f86784ab20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.6
|
Security for buildbot-mattermost-reporter 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.