Re: [Hudson] New Hudson - no longer gives access to workspace without login

2010-08-17 Thread Niklas Gustavsson
On Tue, Aug 17, 2010 at 1:16 AM, sebb wrote: > The previous Hudson installation allowed read-only access to the > workspace without needing a login, however that does not seem to be > possible any more. Should be fixed now, thanks for reporting! /niklas

[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

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

2010-08-17 Thread Uwe Schindler
Hi Niklas, 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 run on any slave that has hadoop label or similar. T

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] New Hudson - no longer gives access to workspace without login

2010-08-17 Thread sebb
On 17 August 2010 08:21, Niklas Gustavsson wrote: > On Tue, Aug 17, 2010 at 1:16 AM, sebb wrote: >> The previous Hudson installation allowed read-only access to the >> workspace without needing a login, however that does not seem to be >> possible any more. > > Should be fixed now, thanks for rep

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 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 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

[Hudson] New Hudson - no longer have access to jobs

2010-08-17 Thread sebb
Not sure if this is due to the host upgrade or the Hudson upgrade. Previously Hudson used to support the notion of "jobs" - small scripts that could be used to fix minor problems in the work area etc. JMeter used to have one which could be used to reset its Version,java file (which otherwise tends

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