Questions regarding Koji, fedpkg and SCM

[Kevin Fenzi]

On Wed, 23 May 2012 17:05:40 -0600
Jeremy Davis <jdavis4102 at gmail.com> wrote:

> Hello List,
> 
> I hope I picked the correct mailing list to ask these types of
> questions.

As noted, the buildsys list might be better. ;) 
> 
> In my environment we are trying to setup a koji build system using
> the same structure that you all use for the Fedora project. This
> involves using fedpkg (modified for our environment) to import the
> SRPM into the SCM and then tell koji to build. We have everything
> working with our environment but have to do a couple of things
> manually. Mainly the SCM creation and adding a tag for the package in
> koji before the user is allow to add their srpm to the SCM and build
> with koji (get the error that it can't tag if a tag is not created
> before hand). Once we create the SCM and add the tag into Koji
> everything works as it should based on the documentation I have read.
> 
> My question is this. Do you by chance have any tools that automate
> the SCM creation and koji tag adding? Is this how you all manage
> packages in Fedora? Do you have to manually create SCM and koji tags
> when a user wants to add a new package to Fedora? Any assistance you
> could provide would be greatly appreciated.

Yes, we use bugzilla to review packages, then we have a script that
takes the approved packages list and processes the new package requests
from it. It's available at: 

http://git.fedorahosted.org/git/?p=fedora-infrastructure.git;a=blob;f=scripts/process-git-requests/process-git-requests;h=37ebbc9c6b1fec0338d082e077bef8856fc1dd21;hb=29e87a22fac82df08e7b31563be5b4bca01f821d

It calls our package database and then goes to the packages machine and
creates the git repo with the needed branches. 

Hope that helps some. 

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20120524/20165cfe/attachment.sig>