Bug 1370383

Summary:	send a message bus notification for each job status change
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	general	Assignee:	Martin Styk <mastyk>
Status:	CLOSED NEXTRELEASE	QA Contact:	Martin Styk <mastyk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	abraverm, jhladky, jtluka, mastyk, mjia, tklohna
Target Milestone:	27.0	Keywords:	FutureFeature, Patch, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-04 07:26:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Callaghan 2016-08-26 06:09:06 UTC

Beaker should support sending messages on a message bus for each (un-finished) job when the status changes. Ideally we would send a message for every sub-component down to the recipe-task level. We could also consider sending a notification for every new recipe-task-result added, but it might make sense to handle that separately.

This would let consumers more efficiently wait for their job status to change, rather than polling in a loop.

bkr job-watch is an example of such a consumer, and it might make sense to port it over to consume these messages as part of this bug too. (It will need to support a polling loop too, for Beaker sites where no message bus is available.)

Comment 2 Dan Callaghan 2018-10-10 01:14:57 UTC

*** Bug 1636054 has been marked as a duplicate of this bug. ***

Comment 3 Jan Tluka 2018-10-10 09:22:49 UTC

Having this implemented would simplify the CI workflows for my team (networking-services) and reduce the resource usage to minimum if we remove active polling the beaker job status from our jenkins instance.

I support this request. +1