James E. Blair bd3ecccb94 Use forced_pipeline with timer events ... As it stands, if multiple pipelines have timers with the same timespec, they will all respond to the events generated for all of them. Instead of matching on the timespec, associate a timer trigger with a pipeline directly. Change-Id: I6a799cc3b59bd7527ace9ee1048bf633dcaa4cd9		2013-12-27 10:38:35 -08:00
..
cmd	Add a promote client command	2013-12-09 08:13:23 -08:00
launcher	Remove unecessary debug message	2013-12-05 13:22:44 -08:00
lib	Revert "report message even if no action is specified"	2013-05-15 14:42:57 +00:00
reporter	Make all changes reportable	2013-12-27 10:22:46 -08:00
trigger	Use forced_pipeline with timer events	2013-12-27 10:38:35 -08:00
__init__.py	Initial commit.	2012-05-29 14:49:32 -07:00
layoutvalidator.py	Make all changes reportable	2013-12-27 10:22:46 -08:00
merger.py	GC git.Repo objects in merger.Repo operations.	2013-11-22 10:32:19 -08:00
model.py	Make all changes reportable	2013-12-27 10:22:46 -08:00
rpcclient.py	Add a promote client command	2013-12-09 08:13:23 -08:00
rpclistener.py	Add a promote client command	2013-12-09 08:13:23 -08:00
scheduler.py	Make all changes reportable	2013-12-27 10:22:46 -08: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