fm-orchestrator

#1037 component reuse is not implemented very efficiently with buildorder
Closed: Invalid by mikem. Opened by ignatenkobrain.

Closed: Invalid
Reopen Issue

It seems that MBS tags components by buildorder, then waiting for repo, then next barch.

I've got 17 levels and only component changed is on the last level, but now I have to wait until MBS will do all this thing.

It could simply tag whatever was < 17 level, wait for it and build my component.

@contyk @mprahl @jkaluza is there any chance to prioritize this?

I was just waiting for 2 hours to reuse 100 components and build just 1 rpm.

https://release-engineering.github.io/mbs-ui/module/2400
https://release-engineering.github.io/mbs-ui/module/2401
https://release-engineering.github.io/mbs-ui/module/2402

See some additional info in #485.

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

dropped

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

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.