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

[Kenny Ho]

On Sun, May 19, 2013 at 2:35 PM, Kenny Ho <kenny.ho at jamdeo.com> wrote:
>> 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?

>I don't see why you'd need to cherry-pick there.  Couldn't you update
>the relevant repos?
I can't update the repos because these changes are actually not merged yet ("patchset-created" in gerrit terms) and can be rejected pending on the result of code review.  I am trying to replicate Pierre Tardy's work back from 2011/2012 (http://video.linux.com/videos/buildbot-and-gerrit-integration-improved-ci-automation) to automate building/testing of patches before they are merged.

Kenny