fedwatch
========
Library for watching fedmsg messages and running arbitrary scripts in a nice way
Think of fedwatch as simple converter from fedmsg json messages into shell
arguments for scripts.
Dependencies
============
* fedmsg (duh!)
* python-dpath (https://github.com/akesterson/dpath-python)
Usage
=====
To use fedwatch you will need to create a configuration file (by default read
from /etc/fedwatch.conf) and scripts that are to be run when messages of
interest arrive (by default /etc/fedwatch.d).
When interesting message arrives, fedmsg converts json data into arguments for
shell scripts and runs each script in <em>script-dir</em> based on
configuration. First argument is always topic so that scripts can handle
different topics.
Real life example of configuration file:
{
"org.fedoraproject.prod.git.receive": {
"args": [
"msg/commit/username",
"msg/commit/repo",
"msg/commit/branch",
"msg/commit/rev",
"msg/commit/summary"
]
}
}
Above configuration means fedwatch will be waiting for <em>git.receive</em>
topic and will pass 6 arguments to any scripts in <em>script-dir</em>:
1. org.fedoraproject.prod.git.receive (topic)
2. FAS username of commiter
3. repository (package) name
4. branch name
5. revision (SHA hash of commit)
6. commit summary (1st line of git commit)
To see list of possible topics and data included in them see
http://fedmsg.readthedocs.org/en/latest/topics/
========
Library for watching fedmsg messages and running arbitrary scripts in a nice way
Think of fedwatch as simple converter from fedmsg json messages into shell
arguments for scripts.
Dependencies
============
* fedmsg (duh!)
* python-dpath (https://github.com/akesterson/dpath-python)
Usage
=====
To use fedwatch you will need to create a configuration file (by default read
from /etc/fedwatch.conf) and scripts that are to be run when messages of
interest arrive (by default /etc/fedwatch.d).
When interesting message arrives, fedmsg converts json data into arguments for
shell scripts and runs each script in <em>script-dir</em> based on
configuration. First argument is always topic so that scripts can handle
different topics.
Real life example of configuration file:
{
"org.fedoraproject.prod.git.receive": {
"args": [
"msg/commit/username",
"msg/commit/repo",
"msg/commit/branch",
"msg/commit/rev",
"msg/commit/summary"
]
}
}
Above configuration means fedwatch will be waiting for <em>git.receive</em>
topic and will pass 6 arguments to any scripts in <em>script-dir</em>:
1. org.fedoraproject.prod.git.receive (topic)
2. FAS username of commiter
3. repository (package) name
4. branch name
5. revision (SHA hash of commit)
6. commit summary (1st line of git commit)
To see list of possible topics and data included in them see
http://fedmsg.readthedocs.org/en/latest/topics/
Metadata
Release files for fedwatch 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fedwatch-0.5.tar.gz | 14.6 kB | Details |
Release files / fedwatch-0.5.tar.gz
| Download URL | fedwatch-0.5.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a81102737537c20b35b2ef1514971b6d6cb5d9442acabdd310a99469d6494643
|
|
BLAKE2b-256 checksum How to use checksums |
b0b17a6214683b09c9a0a6b879fbf4049b09239cc3eec02bcd5556c92997caa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |