[users at bb.net] GitPoller/Scheduler Behavior Changed, Changes Ignored

Aran Deltac bluefeet at gmail.com
Tue Dec 15 18:58:02 UTC 2015


mergeRequests is unset in my configuration.  But, I don't see how that
would play a roll in this as I'm having an issue with separate builders
ignoring changes.  Isn't mergeRequests more about merging builds within a
single builder, not across multiple builders?

Aran

On Fri, Dec 11, 2015 at 2:18 PM Vasily <just.one.man at yandex.ru> wrote:

> Hi,
>
> Didn't read your config yet, but do you set any value to mergeRequests
> configuration variable? Default value of ot might cause the issue you're
> seeing
>
> Thanks,
> Vasily
> 11 дек. 2015 г. 23:19 пользователь "Aran Deltac" <bluefeet at gmail.com>
> написал:
>
>> Hey all,
>>
>> I'm having a weird issue that I've been banging my head on for a couple
>> weeks now without a solution.
>>
>> I have one GitPoller polling for changes on the "master" and "stg"
>> branches.
>>
>> I have 2 SingleBranch schedulers, one for the "master" branch and one for
>> the "stg" branch.
>>
>> I have 6 builders, 4 are attached to the "master" schedulers, and 2 are
>> attached to the "stg" scheduler.
>>
>> How our workflow works is developers make changes on the "master" branch,
>> and then when we are preparing for a release the master branch is promoted
>> to the "stg" branch. * It used to be that when we promoted the master
>> branch to stg that the stg scheduler would kick off new builds.  Now, this
>> is no longer happening, I have to force builds on the stg builders.*
>>
>> Nothing changed that I am aware of as far as configuration of the master,
>> slaves, or the hosts they run on themselves.  Its almost like buildbot is
>> saying "oh, this commit has already been built on the master builders, no
>> need to do it on the stg builders".
>>
>> I've tried all kinds of things.  I've moved the database from SQLite to
>> MySQL.  I've upgraded buildbot from 0.8.9 to 0.8.12.  I've completely wiped
>> the installs of the masters and slaves.  Nothing seems to help.
>>
>> I've also hacked our script which promotes the master branch to the stg
>> branch to include a new dummy commit just so that the stg scheduler sees a
>> change it hasn't seen before.  This works, and fixes the issue, but its
>> just a terrible hack.
>>
>> Here's my master config with @work-specific stuff Xed out:
>> https://gist.github.com/bluefeet/a11ba7330332812ee8e7
>>
>> Any help appreciated!
>>
>> Aran
>>
>> _______________________________________________
>> 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/20151215/1b21e57c/attachment.html>


More information about the users mailing list