taskotron / libtaskotron

#372 Create module build item type in libtaskotron
Closed: Fixed Opened by ralph.

Closed: Fixed
Reopen Issue

The check_compose check here https://github.com/fedora-modularity/check_compose needs to be run in response to a module build.

We therefore are going to need a new item type in runtask to accomodate this new type of artifact to be tested.

We will also eventually need a taskotron-trigger rule for module builds, but I'll file a separate issue for that.

This ticket had assigned some Differential requests:
D1184

Apologies. I didn't describe this very well.

We will also need an MBS directive like the koji directive that, when given a string representing a module build, will pull down the relevant modulemd and rpms for that built module.

@ralph says the changes are going to be needed sometime between F26 branch and GA. Aiming at F26 alpha sounds feasible to me.

After some discussion in #fedora-qa, it sounds like module_build is a good choice for the item_type, as @mkrizek used for trigger in D1180
Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.