[Buildbot-devel] ForceScheduler and codebases

Jared Grubb jared.grubb at gmail.com
Sat Mar 24 17:05:17 UTC 2012


I've been playing with something locally, and wanted to run this idea by everyone ... and also get Harry's opinion, as he might already have something in the works.

First, I created a new Parameter class that represents a drop-down box + text box, which get presented in one line. It basically inherits from the ChoiceParameter class, but populates the property value based on the combination of the drop-down choice and the string (how those mix is configurable).

Then, for each code base, I create one of these parameters, with the drop-down box having the values ['HEAD', "Revision...", "Branch..."]. 'HEAD' causes no sourcestamp to be generated for that codebase. Revision would generate SS={codebase=x, revision=y}; branch gives SS={codebase=x, branch=y}. 

Then, the usual project/repo/branch/revision boxes are removed, since for a multi-codebase builder these are less helpful I think. 

Other thoughts:
* would be nice to allow the drop-down to be extensible, for example, adding specific branches (or renaming 'HEAD'  to trunk or master)
* could use javascript to hide the text box if it's not applicable (ie for the "HEAD" selection)
* so far this is git-specific. For SVN codebases, you might need to be able to specify both revision and branch?
* maybe "Tag" should be available?
* could think about later adding "+patch" and a file chooser





More information about the devel mailing list