Hi All, this is just to thanks everyone on the ml for the support. I solved my issue, but most important I finally understand correctly how this bbot feature works
Best Regards Sergio From: "Alvaro Erickson" <[email protected]> To: [email protected] Sent: Friday, 27 January, 2017 19:27:56 Subject: Re: [[email protected]] Buildbot Triggerable Scheduler and working dir relation Hi Sergio, The Triggered builder will actually run in a different working dir. It will start in its own builder working dir. So, if you want to tell the location of your check-out and compiled code, use the set_properties parameter in the trigger step to pass the location to the Triggered Builder. Then, use interpolation to get the name of your Compiler builder's worker location. Here is an example: steps.Trigger (schedulerNames=['package'], set_properties = {'BuildLoc' : util.Interpolate('%(prop:buildername)s/path/to/compiled code)')} waitForFinish=True) Next, in your PackageBuilder, use interpolation to obtain the 'BuildLoc' property. I hope this helps. Regards, Alvaro On Fri, Jan 27, 2017 at 9:56 AM, Sergio Borghese < [email protected] > wrote: Hi All, just posted the below question on Stackoverflow [ http://stackoverflow.com/questions/41884751/buildbot-triggerable-scheduler-and-working-dir-relation ] Wondering if someone in the ml is able to help me on the topic. Best Regards Sergio Trying to setup a Triggerable Scheduler in buildbot nine (0.9.1) but I think I'm misunderstanding how this is supposed to work. I have two builders: * CompilerBuilder * PackageBuilder Last step of the CompilerBuilder is a trigger step: steps.Trigger (schedulerNames=['package'], waitForFinish=True) The master configuration file has a Triggerable scheduler: c['schedulers'].append(schedulers.Triggerable( name="package", builderNames=['package'])) What I want to achieve/expect * A SingleBranch Scheduler starts the CompilerBuilder * When the CompilerBuilder reaches the last step, the PackageBuilder is triggered, so the freshly compiled software is packaged. What really happens * The SingleBranch Scheduler starts the CompilerBuilder * When the CompilerBuilder reaches the last step, the PackageBuilder is triggered ...so far so good, unfortunately the PackageBuilder is started inside a different working dir from the one where the code has been checked-out and compiled, so the package creation process fails. My understanding was that a Triggered builder would be run in the same working dir of the "calling" builder but I think I'm not understanding how to correctly configure the builders/schedulers correcty. Any hint? -- Sergio Borghese Senior Software Engineer NetResults S.r.l. Via Agostino Bassi 5, 56121 Ospedaletto (Pi), Italy Tel.: +39.050.316.3658 web: www.netresults.it _______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
_______________________________________________ users mailing list [email protected] https://lists.buildbot.net/mailman/listinfo/users
