Email Notifications for Sloth CI Builds
Send email notifications when builds complete or fail.
Executing actions of an app is called build. A build is considered completed if all its actions were completed. If some actions were completed and some failed, it's a partially completed; if all actions fail, the build failed.
This extension sends you emails via SMTP when your builds complete (fully or partially) or fail; just pick the desired notification level, list the recipient emails, and enter your SMTP credentials. Optionally, you can set the subject for each notification level.
Installation
$ pip install sloth-ci-ext-notifications
Usage
extensions:
notifications:
# Use the module sloth_ci_ext_notifications.
module: notifications
# Emails to send the notifications to.
emails:
- foo@bar.com
- admin@example.com
# Log level (number or valid Python logging level name).
# ERROR includes only build fails, WARNING adds partial completions,
# INFO adds completion, and DEBUG adds trigger notifications.
# Default is WARNING.
level: INFO
# The "from" address in the emails. Default is "build@sloth.ci."
from: notify@example.com
# The email subject on build trigger. You can use the {listen_point} placeholder.
# Default is "{listen_point}: Build Triggered."
subject_triggered: 'Triggered build on {listen_point}!'
# The email subject on build completion.You can use the {listen_point} placeholder.
# Default is "{listen_point}: Build Completed."
subject_completed: 'Hooray! {listen_point} works!'
# The email subject on build partial completion. You can use the {listen_point} placeholder.
# Default is "{listen_point}: Build Partially Completed."
subject_partially_completed: 'Better than nothing on {listen_point}'
# The email subject on build fail. You can use the {listen_point} placeholder.
# Default is "{listen_point}: Build Failed."
subject_failed: 'Fail on {listen_point}'
# SMTP settings.
# SMTP mail host and (if not default) port.
# Mandatory parameter.
mailhost: 'smtp-mail.outlook.com:25'
# SMTP login.
login: foo@bar.baz
# SMTP password.
password: bar
# If the SMTP server requires TLS, set this to true. Default is false.
# If necessary, you can provide a keyfile name or a keyfile and a certificate file names.
# This param is used only if the login and password params are supplied.
secure: true
# secure:
# - keyfile
# - cerfile
Metadata
Release files for sloth-ci-ext-notifications 1.0.8
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 | |
|---|---|---|---|---|
| sloth-ci-ext-notifications-1.0.8.tar.gz | 3.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sloth_ci_ext_notifications-1.0.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.6 kB
Release files / sloth-ci-ext-notifications-1.0.8.tar.gz
| Download URL | sloth-ci-ext-notifications-1.0.8.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb937a32cab60a05dae9bebab41cf6bf23a6fecd1794cc6a32a8be3cfe211cea
|
|
BLAKE2b-256 checksum How to use checksums |
f27d262ecafe8156d45d88015a27d7932262ea8873f4e126b9fd36251a51adff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.0a1 CPython/3.9.6 Windows/10
|
Release files / sloth_ci_ext_notifications-1.0.8-py3-none-any.whl
| Download URL | sloth_ci_ext_notifications-1.0.8-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e8eb5c407faf0133f434680d321aefe9ea811d5cdde603f408c3d04253f934a6
|
|
BLAKE2b-256 checksum How to use checksums |
b0323db613c4c44b12ca4c3c4fc731525f86db2e86d573b6308e4e15309766d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.0a1 CPython/3.9.6 Windows/10
|
Security for sloth-ci-ext-notifications 1.0.8
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.