[debexpo-devel] implement autobuilders
ondrej at certik.cz
Sun Feb 1 22:31:18 CET 2009
On Sun, Feb 1, 2009 at 12:25 PM, Jonny Lamb <jonny at debian.org> wrote:
> On Sun, Feb 01, 11:39:47 -0800, Ondrej Certik wrote:
>> Well, I don't want to build it on the server that runs debexpo. Also I
>> want to have a builder for both i386 and amd64, so I will run it on 2
> Oh, this is rather different indeed.
>> So my idea was that debexpo will have some special easy to parse page
>> that will export all packages that need building and my autobuilder
>> will just periodically poll the page and build the package and upload
>> the built package back to debexpo. Debexpo will have to be fixed to
>> accept the binary package from autobuilders and add it to the archive.
> This sounds rather like wanna-build. I think possibly a nicer way than
> having a page to parse would be using the SOAP interface.
Yes, that's already implemented in debexpo.
> However, there's a few issues with this design. How are you proposing
> you send built packages back to the debexpo server? And how are you
> going to verify that these packages are from a trusted location?
> If I answered those two questions myself, I would probably have to write
> another much simpler importer script, and then use some trusted GPG key
> to sign the built packages.
Yes, I'll create a new gpg key for each autobuilder and they will sign
the binary. Debexpo will have the list of gpg keys and only accept
uploads from them.
So the only thing is how to actually import a new binary package and
debexpo should be able to handle it already?
E.g. unless there is something that I don't see, all that I have to do
is to poll the SOAP interface, build the binary package, sign it and
upload it using dput? Why do I need a new importer script?
More information about the debexpo-devel