[Buildbot-devel] trigger a builder from another builder: a bit of confusion

Fulvio Cervone fcervone at me.com
Fri Apr 1 23:05:33 UTC 2011


I will probably go for that way; seems much more easier to implement :)

Thanks!


On Apr 1, 2011, at 4:01 PM, Axel Hecht wrote:

> If you only want to trigger under some condition, have a look at doStepIf in http://buildbot.net/buildbot/docs/0.8.3/Common-Parameters.html#Common-Parameters, that might be useful. 
> 
> Axel
> 
> 2011/4/1 Fulvio Cervone <fcervone at me.com>
> Thanks Axel
> 
> Indeed my setup is much more like  a stripped down setup; was not useful to add complexity while I was trying to understand the setup from the design point of view, so I just oversimplified the setup to get it right.
> 
> I tried it and it works fine; I just wish that i would be able to not have the previous step to fail and halt the builder, to avoid to run always the trigger even when i do not need it (something like if the check step is not successful I would like to halt the build and show a warning instead, but so far was not able to find a way to achieve this, so i just keep in mind that it is not a failure when the check step fail, and the whole check builder fails).
> 
> I will also add the triggerable to B, so i can kick the tests if needed (my build process is kinda messy, so i do not need the tests all the times)
> 
> Thanks for the clarification!
> 
> 
> On Apr 1, 2011, at 3:55 AM, Axel Hecht wrote:
> 
>> C should be the triggerable, and the trigger step is in D.
>> 
>> Now, I'm a tad confused about your setup at large. What people usually do is
>> 
>> Build A on changes to the source code.
>> 
>> If A succeeds, do tests, aka, add a trigger step to A, kicking off a triggerable B.
>> 
>> Not sure why you're running C less frequently, but you could possibly just trigger it from B, if your tests pass.
>> 
>> Axel
>> 
>> 2011/4/1 Fulvio Cervone <fcervone at me.com>
>> Buildbot users/devs,
>> 
>> I am planning to create a builder that will be triggered by a step in another builder...but i am not getting the logic right, so before writing code i would like to know how to get this right from the design perspective.
>> 
>> I have 3 builders:
>> 
>> A that build
>> B that test
>> C that update tools
>> 
>> and a factory for each of them (fA, fB and fC)
>> 
>> each builder has a scheduler set (sA,and sB runs every hour, sC every 8 hours)
>> 
>> now i would like to add a check on C, so if there are certain conditions it will be triggered, so i planned to introduce builder D, that will check and trigger C if the conditions are satisfied.
>> 
>> Looking at the triggerable steps and builders, I get that i have to create a triggerable builder, so I made
>> 
>> Builder D, that has the factory fD(that will run the steps to check if C should be run or not)
>> 
>> and the scheduler sD (triggerable that is pointing to the builder C)
>> 
>> Now where should i put the trigger step? From what I understand it should go in fD, right after the step to check if C should be run or not.
>> 
>> Is this correct or did I got it all wrong ?
>> 
>> Thanks!
>> 
>> ------------------------------------------------------------------------------
>> Create and publish websites with WebMatrix
>> Use the most popular FREE web apps or write code yourself;
>> WebMatrix provides all the features you need to develop and
>> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
>> _______________________________________________
>> Buildbot-devel mailing list
>> Buildbot-devel at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110401/77a9cfaa/attachment.html>


More information about the devel mailing list