On Wed, Apr 14, 2021 at 9:48 AM Honza Horak <hhorak@xxxxxxxxxx> wrote: > > Hi folks, > > I found this thing and thought it might be useful for testing depended > packages before committing, something similar to the chain scratch > builds in koji, that are not available (to my knowledge). > > I didn't realize before we can use module builds for any package set, > that does not even relate to any existing module in Fedora, so sharing > for anybody who finds this useful. > > The use case here is that we have two or more packages that we want to > test before changes land in production branch in dist-git, and where > copr is not enough (for example we want all koji arches). (yes, for many > things copr is much more powerful tool) > > The idea is to run a modular scratch build that picks the packages from > concrete dist-git branches and build them in an expected order. > > The changes must be in a branch in dist-git (not in a fork), but it can > be a private branch. Then we need a modulemd file like this: Note that "private" branches are not really a thing - if they ever were (just look at [postgresql] for a particularly bad example), and if any koji builds are done from those branches, they can *never* be removed again either. So I would strongly advise *not* to do this. Fabio [postgresql]: https://src.fedoraproject.org/rpms/postgresql/branches?branchname=rawhide _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure