Name of builders/testers in buildbot

[Timo Kreuzer]

Hi,

The names for our builders / testers don't seem to be optimal to me. And 
since they seem to be sorted in the waterfall display alphabetically 
now, I suggest renaming them in the following way:
Build_GCCLin_Debug
Build_GCCLin_Release
Build_GCCWin
Build_MSVC_x64
Build_MSVC_x86
Test_KVM
Test_VBox
Test_VMW
Test_VMW_Hybrid
Test_WHS

This way it is much more consistent, limited to actually useful 
information and would sort them nicely with builders left and testers right.

Regards,
Timo

[Colin Finck]

Hi Timo,

Am 17.05.2015 um 10:41 schrieb Timo Kreuzer:
> The names for our builders / testers don't seem to be optimal to me.

Yep, you're right. Our list of builders has grown, so the original
naming scheme is far from perfect.
> Build_GCCLin_Debug
> Build_GCCLin_Release
> Build_GCCWin

Naming one "Debug" and leaving this out for the others doesn't look good
to me. Maybe we'll have a Build_GCCWin_Release someday, this would imply
renaming Build_GCCWin then.
Let's just leave out "_Debug" and have it as an implicit default.
> Build_MSVC_x64
> Build_MSVC_x86

Okay, here we have the architecture as well. But once the x64 version
gets more popular, we'll probably have an x64 GCC builder as well.
Let's simply add the architecture to all builders.
> Test_KVM
> Test_VBox
> Test_VMW
> Test_VMW_Hybrid
> Test_WHS

Yep, this is simple and conveys all information.
So my final suggestion for all builders:

Build_GCCLin_x86
Build_GCCLin_x86_Release
Build_GCCWin_x86
Build_MSVC_x64
Build_MSVC_x86
Test_KVM
Test_VBox
Test_VMW
Test_VMW_Hybrid
Test_WHS

Any other suggestions? Objections?
If not, I'll do the change in the first week of June. That means
changing names in both BuildBot and Testman.

Cheers,

Colin

[Colin Finck]

Am 23.05.2015 um 13:00 schrieb Colin Finck:
> If not, I'll do the change in the first week of June. That means
> changing names in both BuildBot and Testman.

Changes have been applied.
Experiences show that BuildBot changes break things easily, so just
reply here if something has stopped working.

Cheers,

Colin

[Thomas Faber]

"Build GCCLin_x86 Release" now seems to run on every commit AND once a
day, whereas "Build GCCWin_x86" never runs automatically.

Dunno if this was a result of these changes; but the commit trigger
should probably go to the latter one?

Thanks.

On 2015-06-03 21:03, Colin Finck wrote:
> Am 23.05.2015 um 13:00 schrieb Colin Finck:
> > If not, I'll do the change in the first week of June. That means
> > changing names in both BuildBot and Testman.
>
> Changes have been applied.
> Experiences show that BuildBot changes break things easily, so just
> reply here if something has stopped working.
>
> Cheers,
>
> Colin

[Pierre Schweitzer]

Nice catch!

Should be fixed now.

On 14/06/2015 10:02, Thomas Faber wrote:
> "Build GCCLin_x86 Release" now seems to run on every commit AND once a
> day, whereas "Build GCCWin_x86" never runs automatically.
>
> Dunno if this was a result of these changes; but the commit trigger
> should probably go to the latter one?
>
> Thanks.
>
> On 2015-06-03 21:03, Colin Finck wrote:
> > Am 23.05.2015 um 13:00 schrieb Colin Finck:
> > > If not, I'll do the change in the first week of June. That means
> > > changing names in both BuildBot and Testman.
> >
> > Changes have been applied.
> > Experiences show that BuildBot changes break things easily, so just
> > reply here if something has stopped working.
> >
> > Cheers,
> >
> > Colin
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev
-- 
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.