www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Jenkins: Please don't tie jobs to just the windows1 node
Date Mon, 12 May 2014 14:36:02 GMT
Sorry if this derails the thread, but what is the relative workload
tradeoff to infra/builds of maintaining two slaves vs giving windows
projects their own Azure VM so they can install whatever they want?


On 5/11/14 11:56 PM, "Martin Veith" <Martin.Veith@bmw-carit.de> wrote:

>Hi Gav,
>I just tried to switch from windows1 to windows2 in our
>"etch-trunk-windows-x86-experimental" job.
>What I can see so far is that "ant" is not installed.
>As you are then already on the Windows machine maybe you could help us
>also with the missing Visual Studio version >= 2010 (see INFRA-6717 and
>some mails on builds@a.o). We have been already waiting for it half a
>Thanks a lot!
>On So, Mai 11, 2014 at 11:13:42, Gavin McDonald wrote:
>> Thanks Andrew,
>> To expand slightly, we all know that windows2 is lagging behind
>> windows1 in terms of what project dependencies are installed on it.
>> But please DO use windows2 and email here to have any dependencies
>> installed to get us all to a state where your builds will pass
>> (normally) on both slaves.
>> Thanks
>> Gav...
>> On 08/05/2014, at 7:04 PM, Andrew Bayer <andrew.bayer@gmail.com>
>> wrote:
>> > If you've got a job on builds.apache.org that runs on Windows,
>> > please make sure it's set to run on the "Windows" label, not a
>> > specific node
>> > - your job will end up blocked if it's just tied to one.
>> >
>> > A.

View raw message