This is an idea to have a way to define tasks execution for a particular component only. Let's say I have a script that should be run after every build of component A, but it does not make any sense to run it for other components. Taskotron should allow to define that.
One question I have is whether or not there's enough demand to justify putting some solution into the current trigger instead of waiting for the upcoming redesign/reimplementation.
It wouldn't have any fancy webauth but could run off a yaml file (or something equivalent) defining buildname:taskname pairs so that when builds with the right name (directly matching the n in nvr) are seen, the listed taskname is scheduled.
buildname:taskname
I'd really prefer to avoid putting more work into the current trigger unless we have imminent use cases for it, though.
Waiting for redesign is fine to me. Thanks.
Distgit tests are now handled by CI Pipeline. For generic tasks, we have implemented some basic filters, like matching package names by a regexp. I think this ticket was mainly related to distgit tests, so I'll close this as obsolete.
Metadata Update from @kparal: - Issue close_status updated to: Invalid
Login to comment on this ticket.