[Buildbot-devel] Conceptual Questions: Change-based BuildStep

[Kenny Ho]

Hi Dustin,

> Changes are really only messages to say "hey, the source code
> changed".  Your build can get multiple *sourcestamps*, one for each
> codebase, but each sourcestamp corresponds to one change.
> 
> It sounds like you're interested in a case where each change is a new
> head (in hg terms), and when they occur close in time, you want to
> cherry-pick all of them together and build the result.  Is that about
> right?

Um... essentially.  The changes are not from the same codebase or respository though (I am not sure if I am using the term correctly), otherwise I can probably take advantage of the source stability timer and only build the newer head.  I am dealing with Gerrit which is a collection of git repositories.  There are times that I may have changes in the same gerrit project but on different git repositories that may be related.  I have configured the source stability timer to generate only one Build/BuildRequest when this situation happens and I can see that it works (the Build web UI showed that there are multiple ChangeS in one build, and listed them out correctly.)  I am hoping that there is some way for me to put in the BuildStep to say... git cherry pick Change 1 to path 1, Change 2 to path 2 ... to Change N where N is the total number of ChangeS in the Build.  Is this a supported use case?

Regards,
Kenny