[Buildbot-devel] why does 'try' apply patch to triggeredl build?

[Yury Itskovich]

On second thought, I don't really need to do it this way: the test app code doesn't actually depend on the primary app code...  Still, the behavior doesn't seem very intuitive.


-----Original Message-----
From: Yury Itskovich
Sent: Mon 2/16/2009 4:37 PM
To: buildbot-devel at lists.sourceforge.net
Subject: why does 'try' apply patch to triggeredl build?
 
I have a Try_Userpass scheduler that builds my app, and a Triggerable scheduler (with a separate builder/factory) that builds and runs my test app (the test app build depends on the primary app build).  The problem is, Buildbot tries to apply the primary app patch to the test app build as well -- why?  Is there a simple way to prevent this?  Maybe I could override this behavior with a subclass or something, unless I'm missing something obvious.

Thanks,
Yury

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20090216/1ad4b79c/attachment.html>