With this ticket, the docker-autotest check can now be run in libtaskotron but we don't really have a way to schedule it.
It's still not 100% clear on when we should be running the check but an easy place to start is "on every docker build in f23". Create a new package-specific trigger module so that we can get that scheduled in dev, and eventually prod.
This ticket had assigned some Differential requests: D796
I'm freeing up @jsedlak from this ticket. Jan, if you want to do this, definitely claim this. But since this is not directly docker related, but rather taskotron infra, I don't want to push this on you. I'll take it if you don't, I wanted to look at #taskotron-trigger for quite some time anyway. It's up to you :)
Sure, I will do it.
@tflink is it really necessary to create new trigger module? It would be almost the same as KojiBuildCompletedJobTrigger. What about triggering one additional task when package is "docker" in KojiBuildCompletedJobTrigger?
KojiBuildCompletedJobTrigger
No, a new module is probably not needed in this case since we're just running a task on docker builds in this case. Eventually, it'll be run more often (probably with every compose) but that's something we can deal with at a later date.
Fixed in D796.
Login to comment on this ticket.