You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Andrew Bayer <an...@gmail.com> on 2014/05/08 20:04:56 UTC
Jenkins: Please don't tie jobs to just the windows1 node
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.
Re: Jenkins: Please don't tie jobs to just the windows1 node
Posted by Gavin McDonald <ga...@16degrees.com.au>.
On 12/05/2014, at 3:36 PM, Alex Harui <ah...@adobe.com> wrote:
> 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?
Hi Alex,
We are happy to provide both, I know you already have one on the go now; and I
promised to also set Flex up with an 'ASF' Azure Machine too, and I will get to that
this week. Watch this space.!
Gav…
>
> Thanks,
> -Alex
>
> On 5/11/14 11:56 PM, "Martin Veith" <Ma...@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
>> year...
>>
>> Thanks a lot!
>> Martin
>>
>> 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 <an...@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.
>>
>>
>>
>
Re: Jenkins: Please don't tie jobs to just the windows1 node
Posted by Alex Harui <ah...@adobe.com>.
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?
Thanks,
-Alex
On 5/11/14 11:56 PM, "Martin Veith" <Ma...@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
>year...
>
>Thanks a lot!
>Martin
>
>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 <an...@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.
>
>
>
RE: Jenkins: Please don't tie jobs to just the windows1 node
Posted by Martin Veith <Ma...@bmw-carit.de>.
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 year...
Thanks a lot!
Martin
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 <an...@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.
Re: Jenkins: Please don't tie jobs to just the windows1 node
Posted by Gavin McDonald <ga...@16degrees.com.au>.
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 <an...@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.