bzr-builder

recipe from a branch

Bug #455113 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr-builder
Triaged
Medium
Unassigned

Bug Description

It would be nice to be able to have a branch (perhaps one of the ones in the recipe) containing the recipe to be built.

e.g. bzr dailydeb --branch lp:project/daily --path extra/daily-recipe

At the moment having the recipes be on the file system makes distributing/sharing them an out of band thing.,

Revision history for this message
James Westby (james-w) wrote :

I'm working on a "cookbook" feature, that allows you to build
multiple recipes in one go, with some convention as to how
things are done. I could include the ability to specify a branch
from which the recipes are retrieved with that. I think that
might be a better layering, but I can see that for a single
recipe the overhead of the convention may put some people
off.

Thanks,

James

Changed in bzr-builder:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 455113] Re: recipe from a branch

On Mon, 2009-10-19 at 11:09 +0000, James Westby wrote:
> I'm working on a "cookbook" feature, that allows you to build
> multiple recipes in one go, with some convention as to how
> things are done. I could include the ability to specify a branch
> from which the recipes are retrieved with that. I think that
> might be a better layering, but I can see that for a single
> recipe the overhead of the convention may put some people
> off.

I'd be happy putting the recipes in one branch and referring to them; I
wouldn't want to build all the recipes at once as we're doing
just-in-time builds triggered on commits, not on cron.

-Rob

Revision history for this message
James Westby (james-w) wrote :

On Mon Oct 19 20:33:19 UTC 2009 Robert Collins wrote:
> On Mon, 2009-10-19 at 11:09 +0000, James Westby wrote:
> > I'm working on a "cookbook" feature, that allows you to build
> > multiple recipes in one go, with some convention as to how
> > things are done. I could include the ability to specify a branch
> > from which the recipes are retrieved with that. I think that
> > might be a better layering, but I can see that for a single
> > recipe the overhead of the convention may put some people
> > off.
>
> I'd be happy putting the recipes in one branch and referring to them; I
> wouldn't want to build all the recipes at once as we're doing
> just-in-time builds triggered on commits, not on cron.

That's slightly different to what I had in mind then. I'll have
to think about the best way to integrate this.

Note that bzr-builder (of course) uses bzr's transports to retrieve
the file, so it would happily use a link to raw output from
loggerhead. We could also do

  try:
      transport.get(basename)
  except 404:
      b, rp = Branch.open_containing(dirname)
      b.get_file_bytes(os.path.join(rp, basename))

type thing, so you could specify

   bzr dailydeb lp:foo/recipes/whatever

Thanks,

James

James Westby (james-w)
tags: added: medium usability
Revision history for this message
James Westby (james-w) wrote :

Medium importance, as I think it is less urgent with recipes being in LP now.

Thanks,

James

Changed in bzr-builder:
importance: High → Medium
Jelmer Vernooij (jelmer)
Changed in bzr-builder:
status: Triaged → In Progress
assignee: nobody → Jelmer Vernooij (jelmer)
status: In Progress → Triaged
assignee: Jelmer Vernooij (jelmer) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.