Created attachment 67346 [details] [review]
Patch to add --stage parameter to build specific stages

This patch adds a --stage parameter for "build" and "buildone" commands. It lets the user select the stage he wants to run from tinderbox (specifically update, configure, build and install).

If the stage is not supported by the module, it returns with success (needed for meta packages).

One issue with this is that not every module type will use the same set of stage names (e.g. the new "perl" module type has no configure stage).

Perhaps there is a different way of hooking jhbuild up to mozilla tinderbox in a way that provides a better fit?

Stages splitting give us more control over steps execution. Anyway, the only stage I would really require to be run separately is update, and currently there's already an option to do this.

Anyway my implementation offers a limited set of stages (update for checkout/download), configure (autogen+configure stuff), build (make/make all) and install. When you set a stage, it's run until next stage is another one of these 4, and if it's not available it runs silently without returning error (required to avoid problems running non existing steps).

Is there anyway to get a compromise over the name of 3 or 4 common stage names that could be used in a parameter like this one? I think these 4 cover nearly every project (without taking into account make-check's). Maybe I'm a bit biased by autotools projects. These stages would be optional (covering the perl case that do not provide "configure" or others not providing "build"). But a compromise on common names would avoid having configure-like tasks being named in different ways. It there's a compromise like this, this patch would be ok for the stage splitting goal.

Jose, is this patch still necessary for the buildbot work ?  Otherwise I will mark this bug report as obsolete.

Marking bug as obsolete; please feel free to reopen if needed.