This project is Pulse listener that listens to Treeherder’s job cancellation and retrigger actions in ‘exchange/treeherder/v1/job-actions’ and acts upon them.
What it does
worker.py listens to exchange/treeherder/v1/job-actions in an infinite loop.
When it sees a retrigger actions it makes a retrigger request in builapi self-serve using make_retrigger_request from mozci.
When it sees a cancel action it makes a cancel request in buildapi self-serve using make_cancel_request from mozci.
Currently everything is run with dry_run=True, so instead of doing requests the script just logs the requests it would have made.
Current status
worker.py reads exchange and topic from run_time_config.json. It then uses HANDLERS_BY_EXCHANGE, a dictionary defined in config.py to decide what function it will use to handle incoming messages.
Only buildbot topics (e.g. buildbot.#.# or buildbot.try.retrigger) in exchange/treeherder/v1/job-actions are supported for now.
The functions to deal with TH’s job-actions are defined in the module treeherderactions.py
Requirements
mozci
mozillapulse
See bug 1168148 for more details.
1 maintainer
Metadata
1 maintainer
Release files for pulse-actions 0.1.3
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 | |
|---|---|---|---|---|
| pulse-actions-0.1.3.tar.gz | 3.5 kB | Without provenance | Details |
Release files / pulse-actions-0.1.3.tar.gz
| Download URL | pulse-actions-0.1.3.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
077913fca0115ce90b8487c09b232f2f46fe3634bbe963ca67f33de681e7d804
|
|
BLAKE2b-256 checksum How to use checksums |
a2c12c3884b3ca422c65f201026ce675ae03b81d335517f1dc0fdf4e5ef18a32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pulse-actions 0.1.3
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.
