Multiple nightly schedulers

Fri Oct 16 07:59:43 UTC 2015

Hope that helps.

I remember spending about 5-6 hours myself when the default for this
feature got changed in some update trying to understand what was going
on... :)

P.S. Usually the only version which is important is buildmaster (that
varies, obviously, but that is my experience).

Thanks,
Vasily

2015-10-16 9:03 GMT+03:00 Christoph Spielmann <
christoph.spielmann at machineering.de>:

> Hi Vasily,
>
> Thanks for the tip with the merge requests. I think that's what is
> happening in my case i implemented a global function and just return False
> and thus no merging should happen at all. I'll keep an eye on it in the
> next few days... Just for the sake of completeness:
>
> Here's the version info of the master:
>
> Version Information
>
>    - Buildbot: 0.8.12
>    - Twisted: 13.2.0
>    - Jinja: 2.7
>    - Python: 2.7.6 (default, May 29 2014, 08:26:58) [GCC 4.7.3]
>    - Buildmaster platform: linux2
>
> The slaves are not absolutely up2date but at least version 0.8.8 is
> installed.
>
> Thanks again for the tip,
>
> Christoph
>
> Am 15.10.2015 um 21:06 schrieb Vasily:
>
> Hi Cristoph,
>
> First of all, what Buildbot version are you using?
>
> From this vague description it seems to me that build requests from the
> schedulers are getting merged by Buildbot. Try searching for "merge
> requests" in the manual, it's somewhere there... sorry I cannot search it
> myself now as I'm sending this from mobile.
>
> Thanks,
> Vasily
> 15 окт. 2015 г. 13:33 пользователь "Christoph Spielmann" <
> christoph.spielmann at machineering.de> написал:
>
>> Hi everybody,
>>
>> I have a question concerning nightly schedulers but first let me give
>> you some background-information:
>>
>> We are developing native (c++) software under windows in both 64- and
>> 32-bit variants. We used to have two builders, one for each
>> architecture. As it is officially discouraged to let both builders use
>> the same build-directory the original setup consisted of two
>> build-directories one for each architecture. As the code-base grew (new
>> dependencies, updated dependencies...), more and more problems showed up
>> mostly due to the fact that we constantly ran out of hd-space (our
>> buildslaves-hds are already about 100GB tall and we have 5 of them).
>>
>> So i decided to change the configuration in such a way that we only have
>> one builder and we set the desired architecture via a build-property. So
>> far so good, everything works like a charm. If we start the build
>> manually.
>>
>> And now i let me explain my problem:
>>
>> At night we build various branches (currently 3) with both
>> architectures. To make things easier to maintain i setup the nightly
>> builders like this:
>>
>> for branch_name in filelists.keys():
>>     for arch in ["amd64", "x86"]:
>>         c['schedulers'].append(timed.Nightly(name="nightly_" +
>> branch_name + "_" +arch,
>>                     branch=branch_name,#branch='develop',
>>                     builderNames=["installerGeneration"],
>>                     hour=2,
>>                     minute=30,
>>                     onlyIfChanged=False,
>>                     properties={"type": "nightly", "cleanBuild": "true",
>> "arch": arch}))
>>
>> Using this code i end up having 6 different nightly schedulers (at least
>> that's what i would expect...). BUT a few days ago i remarked that there
>> were less than 6 different builds at night. When i checked the builds i
>> remarked the following reason for one of the nightly builds:
>>
>> The Nightly scheduler named 'nightly_develop_x86' triggered this build,
>> The Nightly scheduler named 'nightly_develop_amd64' triggered this build
>>
>> So for one branch one architecture is not built. I monitored the nightly
>> build for a couple of days and had to remark that almost every day one
>> or more builds are missing! The problem is it doesn't occur every night,
>> sometimes it works, sometimes one build is missing, sometimes more...
>> Does anybody have an idea what is going on here?
>>
>> Thanks,
>>
>> Christoph
>>
>> --
>> -------------------------------------------
>> Dipl.-Ing. Christoph Spielmann
>>
>> machineering GmbH & Co. KG
>> Simulation und Automatisierung
>>
>> Wessobrunnerstr. 4
>> 81377 München
>>
>> Tel.: +49(0)89 7800 5274
>>
>> Mobil: +43(0)6802027312
>> Mail: christoph.spielmann at machineering.de
>> Web: www.machineering.de
>> --------------------------------------------
>> machineering GmbH & Co. KG, HRA 94550, Amtsgericht München
>> machineering Verwaltungs-GmbH, HRB 181877, Amtsgericht München
>> Ust-IdNr.: DE268988178, StNr.: 148/212/30579
>> Geschäftsführung: B.Freyer
>> --------------------------------------------
>>
>> _______________________________________________
>> users mailing list
>> users at buildbot.net
>> https://lists.buildbot.net/mailman/listinfo/users
>
>
>
> --
> -------------------------------------------
> Dipl.-Ing. Christoph Spielmann
>
> machineering GmbH & Co. KG
> Simulation und Automatisierung
>
> Wessobrunnerstr. 4
> 81377 München
>
> Tel.: +49(0)89 7800 5274
>
> Mobil: +43(0)6802027312
> Mail: christoph.spielmann at machineering.de
> Web: www.machineering.de
> --------------------------------------------
> machineering GmbH & Co. KG, HRA 94550, Amtsgericht München
> machineering Verwaltungs-GmbH, HRB 181877, Amtsgericht München
> Ust-IdNr.: DE268988178, StNr.: 148/212/30579
> Geschäftsführung: B.Freyer
> --------------------------------------------
>
>
> _______________________________________________
> 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/20151016/440e413a/attachment.html>