On 27. 09. 19 11:50, Fabien Boucher wrote:
I remember that during the Python 3.8 rebuilds in the side tag, one package had
this automated somehow already. I was bumping the release/changelog and trying
to build it in the side tag at least 5 times, but I was building with
--background, so the automation always got the NEVR in Koji first.
I guess it is python-gear ? Where I'm experimenting some automation based on
Zuul CI.
There is a job triggered to build in Koji when master ref change. This job can
be trigger
instead when a PR is closed/merged, that way direct push will not trigger a build.
Yes. I've em-mailed you about the problem when it was happening, asking you to
disable it, there was no reply and I managed to build it at the end.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
