-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Folks,
Few questions/points about the Koji git workflow.
* We have different way to build RPMs in Koji
1/ From source rpm ; you can build any source RPM you submit to the system. e.g: koji build storage7-el7 myNVR.src.rpm
2/ From git ; you send koji an URL + #commit e.g: koji build storage7-el7 "git+https://git.centos.org/git/rpms/tzdata.git?#e24d98" (For that I need to patch kojid so it supports git.c.o schema i.e not having a .spec file directly at / in git)
The proposal is to have both solutions supported but : - - Building from src.rpm will be only trigger by git.c.o and will require special permission. - - SIG users can build their packages but the code need to be in git.c.o (traceability).
What do you think ? Is there a use case where building from src.rpm would be required ?
* Now speaking about the SIG what is the plan for the branches naming ? c${MAJOR}-${SIGNAME} ? I will need to generate this string to checkout the correct branch in git.
Thanks to Fabian the koji installation is being puppetized, and we hope to have some SIG beta-users on board soon.
- -- Thomas