[users at bb.net] Problem with Try Scheduler

Pierre Tardy tardyp at gmail.com
Wed Jan 4 12:25:11 UTC 2017


Hi Katia,

The try Scheduler indeed has some bottlenecks, one of them is that it does
not integrate with codebase
https://github.com/buildbot/buildbot/blob/master/master/buildbot/schedulers/trysched.py#L218
It will hardcoded the codebase to the default ''

Also the patch application mechanism the comes with try does not comply
with the codebase filtering system, which makes both git and hg to try to
apply the patch sent.

There is thus some work to do in order to clean the try + patch system,
which has never been done yet. Please feel free to work on it.

Pierre

Le mar. 3 janv. 2017 à 21:20, Katia De Lu <katiadelu at gmail.com> a écrit :

> Hi all,
>
> Captcha still won't let me register on trac.buildbot.net, so I figured
> I'd report my problem with the Try Scheduler here.
>
> I am using Buildbot version 0.9.1 with a project spread across two
> repositories: one in Git and one in Mercurial.
>
> I am trying to use the TryScheduler to run a series of buildsteps that
> involve both repos.
>
> When I use the 'try' shell command with --vc=hg, it successfully starts a
> build.
>
> However, the build always fails when it reaches the Git checkout step,
> because Buildbot tries to apply the patch to EVERY repo checkout step, not
> just the Mercurial one.
>
> This seems like a bug to me, but I haven't been able to figure out how to
> fix it - nor can I register with Trac to report it.
>
> Can anyone help?
>
> Thanks,
> Kat
> _______________________________________________
> users mailing list
> users at buildbot.net
> https://lists.buildbot.net/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20170104/2c9618d3/attachment.html>


More information about the users mailing list