Re: [Hudson] Problem with jobs tied to slave names

2010-08-22 Thread Niklas Gustavsson
On Tue, Aug 17, 2010 at 3:23 PM, Niklas Gustavsson wrote: > * "hadoopX (Ubuntu)" -> "hadoopX" > * "hudson-solaris (Solaris)" -> "solaris1" > * "hudson-win.apache.org (Windows 2008)" -> "windows1" > * "lucene.zones.apache.org (Solaris)" -> "lucene" > * "minerva.apache.org (Ubuntu)" -> "ubuntu1" > *

Re: [Hudson] Problem with jobs tied to slave names

2010-08-19 Thread Andreas Andreou
Yep, my mistake - it does work, thx. On Wed, Aug 18, 2010 at 10:39, Niklas Gustavsson wrote: > On Wed, Aug 18, 2010 at 4:48 AM, Andreas Andreou wrote: >> Is it possible to add an extra label to the "vesta.apache.org (Ubuntu)" >> slave? >> Somthing like vesta would be fine... Otherwise, there's

Re: [Hudson] Problem with jobs tied to slave names

2010-08-18 Thread Niklas Gustavsson
On Wed, Aug 18, 2010 at 4:48 AM, Andreas Andreou wrote: > Is it possible to add an extra label to the "vesta.apache.org (Ubuntu)" slave? > Somthing like vesta would be fine... Otherwise, there's no way to target > that specific slave Please see my earlier proposal to rename the slaves, in the cas

Re: [Hudson] Problem with jobs tied to slave names

2010-08-17 Thread Andreas Andreou
Is it possible to add an extra label to the "vesta.apache.org (Ubuntu)" slave? Somthing like vesta would be fine... Otherwise, there's no way to target that specific slave On Tue, Aug 17, 2010 at 16:37, Niklas Gustavsson wrote: > On Tue, Aug 17, 2010 at 3:32 PM, Jesse Glick wrote: >> On 08/17/20

Re: [Hudson] Problem with jobs tied to slave names

2010-08-17 Thread Niklas Gustavsson
On Tue, Aug 17, 2010 at 3:32 PM, Jesse Glick wrote: > On 08/17/2010 03:35 AM, Niklas Gustavsson wrote: >> >> I've opened an issue in the Hudson JIRA to see if >> parenthesis in slave names are now invalid. > > I already filed this, maybe make yours a duplicate: > http://issues.hudson-ci.org/browse

Re: [Hudson] Problem with jobs tied to slave names

2010-08-17 Thread Jesse Glick
On 08/17/2010 03:35 AM, Niklas Gustavsson wrote: I've opened an issue in the Hudson JIRA to see if parenthesis in slave names are now invalid. I already filed this, maybe make yours a duplicate: http://issues.hudson-ci.org/browse/HUDSON-7216 Also of interest: http://issues.hudson-ci.org/brows

Re: [Hudson] Problem with jobs tied to slave names

2010-08-17 Thread Niklas Gustavsson
On Tue, Aug 17, 2010 at 9:35 AM, Niklas Gustavsson wrote: > If so, we might have to > rename our slaves. Thinking more about this, how about renaming the slaves to better reflect on their "logical" use in Hudson. Today we use a mixture of TLP names, OSs and physical host names. How about: * "hado

Re: [Hudson] Problem with jobs tied to slave names

2010-08-17 Thread Niklas Gustavsson
On Tue, Aug 17, 2010 at 10:22 AM, Uwe Schindler wrote: > I solved this for Lucene/Solr by adding a label "lucene" to our slave and > entered the label in the input field of the job. This works fine. Using > labels for slaves is a good thing as you can group them. E.g. All builds of > Hadoop only r

RE: [Hudson] Problem with jobs tied to slave names

2010-08-17 Thread Uwe Schindler
> Sent: Tuesday, August 17, 2010 9:36 AM > To: builds@apache.org > Subject: [Hudson] Problem with jobs tied to slave names > > Hi > > In the latest version of Hudson, which we are running, they added boolean > expression support when tying a job to a slave/label. The express

[Hudson] Problem with jobs tied to slave names

2010-08-17 Thread Niklas Gustavsson
Hi In the latest version of Hudson, which we are running, they added boolean expression support when tying a job to a slave/label. The expression language uses parenthesis. So does our slave names. This has caused some job configurations to fail, e.g. when using the string "minerva.apache.org (Ubu