| 2010-02-03 12:01:42 |
Michael Nelson |
description |
Currently the revision of the base branch for a recipe build is specified on the SPRecipe itself (as part of the base_branch specification), but it seems that it would make much more sense (from a users POV), if instead when creating a recipe via the LP UI we always used tip on the recipe (ie. no revision spec on the base branch), and while still allowing the user to specify a revision spec storing it on the SPRBuild.
This would involve adding a base_branch_revision_spec field (or similar) to the SPRBuild table. As far as i can see, it would give us much more re-usability of recipes (as well as other minor advantages, like not allowing a daily build of a specific base_branch revision to be specified). It would only affect/restrict base_branches of recipes (all other merges in the recipe are free text and so revisions can be specified as needed).
Thoughts? (Idea via beuno's suggestion on mailing list). |
Currently the revision of the base branch for a recipe build is specified on the SPRecipe itself (as part of the base_branch specification), but it seems that it would make much more sense (from a users POV), if instead when creating a recipe via the LP UI we always used tip on the recipe (ie. no revision spec on the base branch), and while still allowing the user to specify a revision spec storing it on the SPRBuild.
This would involve adding a base_branch_revision_spec field (or similar) to the SPRBuild table which would be used together with the SPRDataInstruction for the base_branch. As far as i can see, it would give us much more re-usability of recipes (as well as other minor advantages, like not allowing a daily build of a specific base_branch revision to be specified). It would only affect/restrict base_branches of recipes (all other merges in the recipe are free text and so revisions can be specified as needed).
Thoughts? (Idea via beuno's suggestion on mailing list).
|
|
