fm-orchestrator

#1022 Add a RepoResolver
Closed: Duplicate by ralph. Opened by ralph.

Closed: Duplicate
Reopen Issue

Today, when doing a build, you need one resolver plugin to be activated.

  • The MBS server uses the DBResolver, to query its own database directly.
  • Local builds typically use a MBSResolver, in order to query for available builds from a remote MBS instance.

We need the ability to perform builds against modules when the MBS instance they were built in is not accesible. If those builds were completed, and composed, and made available in a yum repository with a modulemd metadata file baked in, in principle MBS should be able to read that repository, know about the modules and build more modules on top of them. This is similar to how you can use the rpms in the end-user fedora repos to build more rpms. You should be able to use the end-user module repos to build more modules.

To do this, we should give MBS a new RepoResolver which can resolve deps from one or more provided repo urls.

This is very close to current --offline local builds. For these builds, the repository with modules is taken from /etc/yum.repos.d/ directory. We could easily extend it to enable repos from any URL.

As a workaround, you can also just define .repo file in /etc/yum.repos.d/ directory pointing to repo you want.

Oh, that works! Thanks. (This was essentially a request in anticipation of CentOS rebuilds. If we can handle that or are getting ready to handle that, then this can be closed as irrelevant.)

Metadata Update from @ralph:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

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

Please continue any further discussion there.
Metadata
None
None
None
None
None
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.