On Thu, Oct 22, 2020 at 09:42:30AM +0200, Bruno Goncalves wrote:
It is not expected, the test should trigger once the update lands on
In this case for some reason the pipeline missed the trigger message.
We are in the process of moving the pipeline to a new cluster that
should help in cases like this.
Anyway, I've triggered it manually now:
Btw, you should be able to retrigger the test by running "bodhi
updates trigger-tests <update id>"
Any chance of making this available in the Bodhi WebUI? For these
tasks that are only rarely needed, reminding people visually what the
possible actions are might be useful.
Product Owner, Platform Security Readiness, Red Hat