Hm... this would be fine.

I think I was originally thinking that this would be part of the continuous-compose service instead of the module-build service.

Question: do we only do auto-rebuilds like this for stacks, or for all defined modules?

I faintly remember you used to have an arrow from dist-git directly to MBS on that old architecture picture... hmm. Am I misremembering?

I meant this to replace the "fedpkg module-build" command, whether it's an automatic rebuild or a true update triggered by a human.

I realize having this enabled now wouldn't do us any good but I wanted to ask about the status and whether this will be enabled once you deploy MBS in production. It'd be useful even from the CI POV -- everything you push gets built / tested.

It is very easy to implement - we just have to listen for dist-git commit fedmsg message and call submit_module_build with the scmurl provided in that dist-git message.

It is more political question - do we want to build every commit? It's shift from our current way of work with "fedpkg build". We could probably trigger something like "scratch" build, but we do not have scratch builds of whole modules so far.

This is handled by freshmaker (in code). Will be solved once we have fedora-infrastructure#6183.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/mbs/issues/199

Please continue any further discussion there.