On Thu, Oct 22, 2020 at 9:55 AM Jan Pazdziora <jpazdziora(a)redhat.com> wrote:
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
> "testing" state.
> 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:
>
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-f33-build-...
Thanks.
> 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.
For that I think you need to open an RFE for Bodhi, I'm not sure what
is the best place for it, maybe on
--
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat
_______________________________________________
CI mailing list -- ci(a)lists.fedoraproject.org
To unsubscribe send an email to ci-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org