Hi Pierre,
In our case, restarting masters is annoying to others. It may be better
for us to switch back to the original branch and reconfigure (because we
don't actually care if any of those builds schedules). This should
remove the scheduler we don't want. Switch back to the current branch
and reconfigure, and all the master should have the correct builders.
Our base problem is that a couple of builders were switched to the new
branch a while ago, which is why the scheduler of that name existed.
When we switched branches for the rest of the builders, they never got
in because that scheduler already existed.
Neil Gilmore
grammatech.com
On 11/4/2016 11:02 AM, Pierre Tardy wrote:
Hi Neil and Pieter,
This is a known problem in buildbot nine that schedulers are not
reconfigurable.
The need to implement the reconfigureService API, which they don't.
This is not a big amount of work, but this has not been done yet.
http://trac.buildbot.net/ticket/2237
The workaround is to change the scheduler name so that it is forced
re-created.
Please feel free to dig in the code and submit a PR if this becomes
too annoying.
Regards,
Pierre
Le ven. 4 nov. 2016 à 16:51, Neil Gilmore <[email protected]
<mailto:[email protected]>> a écrit :
(managed to not reply to the list the first time...)
On 11/4/2016 9:02 AM, Neil Gilmore wrote:
> Hi Pieter,
>
> Thanks for the reply and explanation. It's nice to know that someone
> else experiences this.
>
> It would also explain a previous problem we had where someone
updated
> the configuration to move a daily builder to a new time, and it
would
> never schedule.
>
> I can do restarts, but it's socially painful (people notice and
> complain immediately). Keeping history isn't a problem, though,
as we
> send all our build results to a different, more comprehensive
system.
>
> Neil Gilmore
> grammatech.com <http://grammatech.com>
>
> On 11/4/2016 2:48 AM, Pieter Lexis wrote:
>> Hello Neil,
>>
>> On Thu, 3 Nov 2016 16:27:11 -0500
>> Neil Gilmore <[email protected]
<mailto:[email protected]>> wrote:
>>
>>> It seems that after a branch change and reconfig, our buildbot
>>> system is
>>> misbehaving. Builds are not getting scheduled.
>>> <SNIP>
>> I have been experiencing similar 'issues' since beta 2 (I
believe). I
>> don't update the configuration often, so I hardly notice. This is
>> with a single master.
>>
>> But e.g. adding a builder to a scheduler and reloading the
config. It
>> appears that that this is not picked up. After a restart (which
I can
>> do on the platform I'm running), all is well.
>> However, I once forgot to restart and noticed the next day that
after
>> some time the changes were picked up, leading me to believe that
>> buildbot might keep some old state around, although I have not been
>> able to reproduce this in a test environment.
>>
>> Best regards,
>>
>> Pieter
>>
>
_______________________________________________
users mailing list
[email protected] <mailto:[email protected]>
https://lists.buildbot.net/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.buildbot.net/mailman/listinfo/users
