zuul/zuul
Joshua Hesketh 1879cf721c Separate reporters from triggers
Allows multiple reports per a patchset to be sent to pluggable
destinations. These are configurable per pipeline and, if not
specified, defaults to the legacy behaviour of reporting back only
to gerrit.

Having multiple reporting methods means only certain success/failure
/start parameters will apply to certain reporters. Reporters are
listed as keys under each of those actions.

This means that each key under success/failure/start is a reporter and the
dictionaries under those are sent to the reporter to deal with.

Change-Id: I80d7539772e1485d5880132f22e55751b25ec198
2013-08-29 13:17:12 +10:00
..
cmd Separate reporters from triggers 2013-08-29 13:17:12 +10:00
launcher Re-launch a job if the worker fails to run it 2013-08-23 15:17:33 -07:00
lib Revert "report message even if no action is specified" 2013-05-15 14:42:57 +00:00
reporter Separate reporters from triggers 2013-08-29 13:17:12 +10:00
trigger Separate reporters from triggers 2013-08-29 13:17:12 +10:00
__init__.py Initial commit. 2012-05-29 14:49:32 -07:00
layoutvalidator.py Separate reporters from triggers 2013-08-29 13:17:12 +10:00
merger.py Revert bogus merger optimizations 2013-08-27 17:14:51 -07:00
model.py Separate reporters from triggers 2013-08-29 13:17:12 +10:00
scheduler.py Separate reporters from triggers 2013-08-29 13:17:12 +10:00
version.py Migrate to pbr. 2013-06-25 19:04:30 +00:00
webapp.py Add a JSON status test 2013-07-06 18:20:54 +00:00