On Thu, Feb 27, 2020 at 5:04 PM Jan Pazdziora <jpazdziora(a)redhat.com> wrote:
On Thu, Feb 27, 2020 at 04:56:28PM +0100, Bruno Goncalves wrote:
>
> That is interesting, it looks like the pipeline didn't trigger because
> bodhi didn't send a message for it.
>
> At least the only recent message that it sent about this package
> recently was for rawhide....
>
https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.pr...
>
Thank you for looking into it.
Does that sound like a bug in bodhi, so something to file an issue at
https://github.com/fedora-infra/bodhi/issues
for?
I'm not sure either, I'd rather if someone with more experience with
bodhi could say when
"org.fedoraproject.prod.bodhi.update.status.testing.koji-build-group.build.complete"
is sent.
Or if we should trigger with some other topic...
I've been triggering on it since
https://pagure.io/fedora-ci/general/issue/70
Is the only way to force that CI job to run to make bodhi send the
message?
I've rescheduled it manually, let's see how it goes...
https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-rawhide-bu...
--
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