Hello,

after talking to several teams who are using Beaker for the CI we have realized that there is a common pattern. There is an automatic CI job (either Jenkins or Upshift container) which will start a Beaker job and it then waits for the Beaker job to finish, polling the status every few minutes via bkr job-watch.

Since Beaker jobs often take several hours to complete (waiting for the resources) we waste the resources by having Jenkins / container allocated all the time waiting for the Beaker to finish. It also creates unnecessary load on the Beaker side when tens or even hundreds of jobs are polling Beaker job status. 

We could solve the problem by adding support for the message bus to the Beaker. The idea is that Beaker would send a message to UMB whenever a Beaker job status would change the state. 

We believe that the whole kernel QE and engineering department would benefit from this enhancement along with other teams. It has been discussed on the kernel-ci mailing list and got a wide support. 

Thanks a lot for considering this RFE. 
Jirka