On Fri, Feb 1, 2019 at 4:48 PM Kevin Fenzi <ke...@scrye.com> wrote: > >>> It is not official build system of Fedora which is not helping with > >>> Problem > >>> №2: Testing of new rpm/koji/mock features/configuration > >>> > >>> <https://docs.google.com/document/d/1DtNTCa-gXc0ILDDHPyAcAca2GGGlENavfgPwGGgqJ_Y/edit#heading=h.iodoq4xw80c2> > >> > >> Note that if you also are testing new things you could break packagers > >> that are trying to do other work... > > > > Testing new features would be done in separate tags. So no, others > > would not be affected. > > I'm not sure how you could test a new koji hub or rpm on the hub with > tags, but sure, you could test some things by having different builders.
Testing new rpm features, global macros etc. can be done by tagging a build (of rpm, redhat-rpm-config etc.) into one tag without affecting other tags. Testing new kojid/mock configuration can be done on builders in non-default channels. For testing new Koji releases we have staging setup. > >>> By building only on a single, fast architecture. > >> > >> This may well bite you when you merge back to koji and build for all > >> arches. > > > > I don't see this as a problem.Most of the packages that we are > > planning to build in MBI (Java/Rust/Go) are noarch anyway. > > ok. Unless some other folks start using it. Then we can reconsider more architectures later. Or they can contribute their builders of any architectures, even not supported by Fedora Koji. -- Mikolaj _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
