launchpad-dev team mailing list archive

[Jonathan Lange <jml@xxxxxxxxxxxxx>]

On Tue, Oct 6, 2009 at 8:48 PM, Julian Edwards
<julian.edwards@xxxxxxxxxxxxx> wrote:
> Hey Tim
>
> We said we'd have a chat about the BFB requirements and design before deciding
> on a sprint.
>
> As I understand it, the things we want are:
>
>  * A PPA picker on the source package branch page with a "Build" button
>    (and we might want to extend this to a distro upload at some point)
>

It should be an archive picker, not a PPA picker, I think.

Even if we don't want to allow builds to the main archive initially,
this should be a property of the archive (or a linked archive policy),
not of the UI widget.

>  * The button will create a job request to run `bzr builddeb` or equivalent.
>
>  * The job will need to run in a secure environment; the existing Soyuz build
>    farm is most appropriate for this.  It will need a new set of chroots to
>    run this command (or any arbitrary jobs I guess).
>
>  * We will need to make our buildd-manager to handle this generic job type
>    in tandem with the other package builds.  This is where most of the work
>    lies.
>

I agree with both sentences in this point. I'm guessing that this will
involve a fair amount of cleanup.

Will there be much opportunity here to address things like build scheduling?

>  * It's also possible that the branch build will fail so an email should be
>    sent in that case.
>

Ideally, this would just use the regular Job system for failed jobs.
If that doesn't exist yet, we should create one :)

>  * At this point the regular Soyuz package build mechanisms continue as
>    normal.
>
> I've made no mention of any UI beyond the first point, as I'm not sure we need
> anything else.  We can enhance the existing /builders page to give more info
> on waiting BFBs.  Can you think of any other UI changes we'd need?
>

Not off the top of my head. I do think that we should be mindful of
building a good UI for long-running, potentially failing jobs like
this, and that we should use that UI across Launchpad.

> As far as I can see, most of the work needs to be done in the Soyuz domain.
> We'll also need some assistance from the IS guys to get the appropriate
> chroots made to their security standards.
>
> Did I miss anything?
>

There's nothing here about building private branches to private
archives. We should at least think about that.

There's a spec at https://dev.launchpad.net/BuildBranchToArchive based
on the discussions at the Karmic UDS, and a mailing list thread at
https://lists.launchpad.net/launchpad-dev/msg00256.html. Both of these
are at least worth skim-reading.

jml