Re: Sharing my views

2013-11-15 Thread Vincent Latombe
All views you have created so far are public views. Anyone will see them.

Vincent


2013/11/15 CLOSE Dave 

> I'm a bit confused by the "view" mechanism in Jenkins.
>
> I have created several additional views for my own use using the "+" on
> the tab bar. When I click "My views" on the left menu, only the default
> view is shown. Yet every time I connect, I see all the tabs I saw the
> previous time.
>
> I know that I can change the default view when users connect to Jenkins.
> In the "Manage Jenkins" menu, I see all the personal views I created
> listed as alternative choices. But I can select only one as the default
> view.
>
> What I'd like to do is to allow other users to see all the same tabs I
> see, without each of them needing to create all those views on their
> own. Is that possible?
> --
> Dave Close, Thales Avionics, Irvine California USA.
> cell +1 949 394 2124, dave.cl...@us.thalesgroup.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Sharing my views

2013-11-15 Thread CLOSE Dave
I'm a bit confused by the "view" mechanism in Jenkins.

I have created several additional views for my own use using the "+" on 
the tab bar. When I click "My views" on the left menu, only the default 
view is shown. Yet every time I connect, I see all the tabs I saw the 
previous time.

I know that I can change the default view when users connect to Jenkins. 
In the "Manage Jenkins" menu, I see all the personal views I created 
listed as alternative choices. But I can select only one as the default 
view.

What I'd like to do is to allow other users to see all the same tabs I 
see, without each of them needing to create all those views on their 
own. Is that possible?
-- 
Dave Close, Thales Avionics, Irvine California USA.
cell +1 949 394 2124, dave.cl...@us.thalesgroup.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: Problem with Build Flow Plugin

2013-11-15 Thread Jeremy Morton
Email notifications at the end of Job2 are one of the things that cause it 
to wait for all previously started runs to finish in order to compare 
results. :(

On Friday, November 15, 2013 12:58:17 PM UTC-5, James Nord (jnord) wrote:
>
>  That’s not the flow that’s stopping it but job2.
>
>  
>
> Most likely you have some post build reports (configuration ) that compare 
> to the previous run to generate new/resolved issues (e.g. test results, 
> static anlaysis with new violations identified…)
>
>  
>
> /James
>
>  
>   
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Zofia Majenka
> *Sent:* 15 November 2013 17:13
> *To:* jenkins...@googlegroups.com 
> *Subject:* Problem with Build Flow Plugin
>  
>  
>  
> Hi,
>
> We are using the Build Flow Plugin in Jenkins. This is scenario:
>
> Start the flow 1: Job1 -> Job2 -> Job3 
>
> Start the flow 2: Job1 -> Job2 -> Job3 
>
> Start the flow 3: Job1 -> Job2 -> Job3 
>
> The same flow is started 3 times with a few minutes delay between them. 
>
> We have noticed that thought the Job2 in the flow 3 is finished, it hangs 
> on upstream notification and the Job3 within the same flow 3 could not be 
> started. It waits until the Job2 in flow1 is finished and  Job2 in flow2 is 
> finished. 
> Is it how it always works? The same job started in parallel (several 
> execution of the same test flow on different resources) tends to become a 
> serial? 
>
>
> Start Job2 flow1
> Start Job2 flow2
> Start Job2 flow3
>
> Finish Job2 flow1
> Finish Job2 flow2
> Finish Job2 flow3
>
> Is it possible to start as above but finish like this:
>
> Finish Job2 flow3 and start Job3
> Finish Job2 flow2 and start Job3
> Finish Job2 flow1 and start Job3
>
>
> Or there is something in configuration we are missing? The job is 
> configured to be executed in parallel.
>
> Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 
> takes long time to execute?
>
> Regards
> /Zofia
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>   

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


RE: Problem with Build Flow Plugin

2013-11-15 Thread James Nord (jnord)
That's not the flow that's stopping it but job2.

Most likely you have some post build reports (configuration ) that compare to 
the previous run to generate new/resolved issues (e.g. test results, static 
anlaysis with new violations identified...)

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Zofia Majenka
Sent: 15 November 2013 17:13
To: jenkinsci-users@googlegroups.com
Subject: Problem with Build Flow Plugin

Hi,

We are using the Build Flow Plugin in Jenkins. This is scenario:

Start the flow 1: Job1 -> Job2 -> Job3 

Start the flow 2: Job1 -> Job2 -> Job3 

Start the flow 3: Job1 -> Job2 -> Job3 

The same flow is started 3 times with a few minutes delay between them.

We have noticed that thought the Job2 in the flow 3 is finished, it hangs on 
upstream notification and the Job3 within the same flow 3 could not be started. 
It waits until the Job2 in flow1 is finished and  Job2 in flow2 is finished.
Is it how it always works? The same job started in parallel (several execution 
of the same test flow on different resources) tends to become a serial?


Start Job2 flow1
Start Job2 flow2
Start Job2 flow3

Finish Job2 flow1
Finish Job2 flow2
Finish Job2 flow3

Is it possible to start as above but finish like this:

Finish Job2 flow3 and start Job3
Finish Job2 flow2 and start Job3
Finish Job2 flow1 and start Job3


Or there is something in configuration we are missing? The job is configured to 
be executed in parallel.

Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 takes 
long time to execute?

Regards
/Zofia
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Problem with Build Flow Plugin

2013-11-15 Thread Zofia Majenka
Hi,

We are using the Build Flow Plugin in Jenkins. This is scenario:

Start the flow 1: Job1 -> Job2 -> Job3 

Start the flow 2: Job1 -> Job2 -> Job3 

Start the flow 3: Job1 -> Job2 -> Job3 

The same flow is started 3 times with a few minutes delay between them. 

We have noticed that thought the Job2 in the flow 3 is finished, it hangs 
on upstream notification and the Job3 within the same flow 3 could not be 
started. It waits until the Job2 in flow1 is finished and  Job2 in flow2 is 
finished. 
Is it how it always works? The same job started in parallel (several 
execution of the same test flow on different resources) tends to become a 
serial? 


Start Job2 flow1
Start Job2 flow2
Start Job2 flow3

Finish Job2 flow1
Finish Job2 flow2
Finish Job2 flow3

Is it possible to start as above but finish like this:

Finish Job2 flow3 and start Job3
Finish Job2 flow2 and start Job3
Finish Job2 flow1 and start Job3


Or there is something in configuration we are missing? The job is 
configured to be executed in parallel.

Any ideas? How we can make the flow 3 to finish thought the Job2 in flow1 
takes long time to execute?

Regards
/Zofia

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: sloccount plugin

2013-11-15 Thread Daniel Beck
On 15.11.2013, at 17:40, "Kevin Fleming (BLOOMBERG/ 731 LEXIN)" 
 wrote:

> it's not clear whether there has been a new release of the sloccount plugin 
> that includes the fix or not

Not directly related to the thread topic, but click the link to the commit on 
Github in the Jira comments section, and it'll tell you in which releases that 
particular change is in. In this case, there's only one related commit:

https://github.com/jenkinsci/sloccount-plugin/commit/510d0a7611d8a31e2bccb0c7bbd7e21bcf6c600d

And it is in (click the ellipsis on Github):

• master
• sloccount-1.10
• sloccount-1.9.1
• sloccount-1.9
• sloccount-1.8

It's not a 100% solution (it'll still show up even when a later commit reverts 
all changes), but it's still really useful.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: sloccount plugin

2013-11-15 Thread Kevin Fleming (BLOOMBERG/ 731 LEXIN)
The first thing I'll suggest is that you exhibit a bit of patience; as you've 
been told before on this list, most of the people here are volunteering their 
time, and have plenty of other things to do, so they aren't going to drop 
everything they are doing to answer your questions.

Your problem appears to be this one: 
https://issues.jenkins-ci.org/browse/JENKINS-4836

That is marked as 'fixed', but it's not clear whether there has been a new 
release of the sloccount plugin that includes the fix or not. There are 
multiple issues in JIRA about running sloccount under Windows, so you should 
likely review all of them see if any of them apply to your situation.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Nov 15 2013 05:04:40

please suggest

regards


On Fri, Nov 15, 2013 at 6:17 AM, Irfan Sayed  wrote:

thanks.

i configured job for sloccount plugin.
my environment is windows and i configured Cygwin to run the sloccount 
so there are two commands which i run to debug ...

1: 
/cygdrive/c/Users/bvcontrolbuild/Downloads/sloccount-2.26/new/sloccount-2.26/sloccount
 --duplicates --wide --details 
/cygdrive/c/workspace/ua_final/DataIntegration/di-core/src/main/ > 
/cygdrive/c/workspace/ua_final/DataIntegration/sloccount.sc

the output of above command is stored in file sloccount.sc file . PFA

2: 
/cygdrive/c/Users/bvcontrolbuild/Downloads/sloccount-2.26/new/sloccount-2.26/sloccount
 /cygdrive/c/workspace/ua_final/DataIntegration/di-core/src/main/ > 
/cygdrive/c/workspace/ua_final/DataIntegration/sloccount.sc

the output of above command is stored in file sloccount1.sc. PFA

so first thing is , i don't know which command i should go ahead with ?
second, in Jenkins job configuration , if i put file sloccount1.sc file , then 
it does not throw any exception , but, at the end , there is no any report also 
and no any trend graph also 

further, if i put sloccount.sc file , then jenkins throws follwoing exception 
at the end of build 


Started by user Irfan Sayed [EnvInject] - Loading node environment variables. 
Building remotely on 10.211.162.150 in workspace C:\workspace\ua_final 
[ua_final] $ cmd /c call 
C:\Users\BVCONT~1\AppData\Local\Temp\2\hudson4372201469243593858.bat  
C:\workspace\ua_final>C:\cygwin64\Cygwin-jenkins.bat bash: cannot set terminal 
process group (-1): Inappropriate ioctl for device bash: no job control in this 
shell ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due 
to exception java.lang.StringIndexOutOfBoundsException: String index out of 
range: -1 at java.lang.String.substring(String.java:1911) at 
hudson.plugins.sloccount.model.SloccountReport.extractFolder(SloccountReport.java:71)
 at 
hudson.plugins.sloccount.model.SloccountReport.add(SloccountReport.java:49) 
at 
hudson.plugins.sloccount.model.SloccountParser.parseLine(SloccountParser.java:99)
 at 
hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:66)   
  at 
hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:57)   
  at 
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:47)  
   at 
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17)  
   at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2420) 
at hudson.remoting.UserRequest.perform(UserRequest.java:118) at 
hudson.remoting.UserRequest.perform(UserRequest.java:48) at 
hudson.remoting.Request$2.run(Request.java:326) at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)  
   at java.util.concurrent.FutureTask.run(FutureTask.java:166) at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
at hudson.remoting.Engine$1$1.run(Engine.java:61) at 
java.lang.Thread.run(Thread.java:724) Notifying upstream projects of job 
completion Finished: FAILURE 
please suggest me where i m going wrong 

regards


On Fri, Nov 15, 2013 at 12:45 AM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) 
 wrote:
  
Please don't crosspost messages to multiple mailing lists.

Yes, some of us use the sloccount plugin. It's pretty much impossible to help 
you in any useful way if you don't tell us what problems you are experiencing, 
though.


- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-...@googlegroups.com, jenkinsci-users@googlegroups.com


At: Nov 14 2013 14:05:28

hi,

have anybody used the sloccount plugin.??
i have couple of doubts with which i am struggling 

please let me know 

regards
irfan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
  To unsubscribe from this group and stop

Re: Disk usage trend report wrong?

2013-11-15 Thread Vojtech Juranek
Hi,

> The upper left line tells me:
> Jobs:2 GB, Builds:2 GB, Locked builds:-, Workspace:10 GB
> 
> The actual size of the workspace folder is around 11.6 GB.
> 
> The graphical Disk usage trend report shows me a workspaces
> size of 2 GB.

there could be some issues with calculation of disk usage in 0.21 and older 
releases (and thus disk usage could be wrong in some cases). There were some 
major changes implemented in 0.22 - please update to the recent 0.23 and if 
you are already on 0.23, it's IMHO a bug. Then please file a bug under disk 
usage component in Jira [1].

> In the bug database I found [bugreport 3003], but the attempt of an
> explanation there confuses me even more.

this issue was about something different - the requester expected, that the 
graph shows sum of all builds (i.e. cumulative graph), but the graph shows 
only sizes of given builds (i.e. in plot is size of builds #1, size of builds 
#2 etc.). This behavior hasn't changes and plot still shows sizes of 
individual builds.

HTH
Vojta

[1] https://issues.jenkins-ci.org/browse/JENKINS/component/15537

signature.asc
Description: This is a digitally signed message part.


Disk usage trend report wrong?

2013-11-15 Thread scl

Hi,

I'm having problems with the disk usage report.

The upper left line tells me:
Jobs:2 GB, Builds:2 GB, Locked builds:-, Workspace:10 GB

The actual size of the workspace folder is around 11.6 GB.

The graphical Disk usage trend report shows me a workspaces
size of 2 GB.

These values are all fresh records.

I'm wondering about these differences and in fact especially
the graphicall report isn't of use at all if it's so wrong.
In the bug database I found [bugreport 3003], but the attempt of an 
explanation there confuses me even more.

Can anybody shed some light on these differences, please?

Thank you in advance,

Sven

[bugreport 3003]:
https://issues.jenkins-ci.org/browse/JENKINS-3003

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: Label restriction issue

2013-11-15 Thread Thomas
Was actually a typo error
Sorry for the noise

By the way, 
The advise about how to check the slaves that match an expression was 
really helpful
Thanks
Thomas



Le vendredi 15 novembre 2013 10:17:09 UTC+1, Daniel Beck a écrit :
>
> This should work. 
>
> Open http://yourjenkins/label/LABEL1&&LABEL2&&!NODE_NAME -- which slaves 
> does it show to match this expression? Is the one this should not run on 
> listed as well? 
>
> On 15.11.2013, at 10:06, Thomas > 
> wrote: 
>
> > Hi, 
> > 
> > I am encountering an issue with Label restrictions: 
> > I want a job to be dispatched on a slave node that has labels LABEL1 and 
> LABEL2 but different from NODE_NAME. 
> > Thus, in the "Restrict where this project can be run", I specified an 
> expression such as: 
> > LABEL1 && LABEL2 && !NODE_NAME 
> > 
> > but unfortunately, my job starts on NODE_NAME. 
> > 
> > Is there something wrong in my setup or is this an issue with labels ? 
> > 
> > Thanks 
> > Thomas 
> > 
> > (using jenkins 1.538) 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "Jenkins Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to jenkinsci-use...@googlegroups.com . 
> > For more options, visit https://groups.google.com/groups/opt_out. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: Maven Dependency Update trigger not working for version ranges

2013-11-15 Thread Christoph Kutzinski

Do you have a test case to reproduce it?
Maven version ranges should be supported since Jenkins 1.481

(see https://issues.jenkins-ci.org/browse/JENKINS-12735)


Am 15.11.2013 12:18, schrieb Bacon, Keith:

Does anyone else wish this would work for version ranges?
Is there a good reason why it doesn’t or can’t?
Thanks,
Keith

--
You received this message because you are subscribed to the Google
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Maven Dependency Update trigger not working for version ranges

2013-11-15 Thread Bacon, Keith
Does anyone else wish this would work for version ranges?

Is there a good reason why it doesn't or can't?

Thanks,
Keith

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: How to remove disk-usage plugin completely?

2013-11-15 Thread dennys
It works. But I found I need to load the jobs and then I can unload them.
It means that I load every job and need to show all the version and Jenkins
will load them.



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/How-to-remove-disk-usage-plugin-completely-tp4679890p4680307.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: sloccount plugin

2013-11-15 Thread Irfan Sayed
please suggest

regards



On Fri, Nov 15, 2013 at 6:17 AM, Irfan Sayed  wrote:

> thanks.
>
> i configured job for sloccount plugin.
> my environment is windows and i configured Cygwin to run the sloccount
> so there are two commands which i run to debug ...
>
> 1: 
> /cygdrive/c/Users/bvcontrolbuild/Downloads/sloccount-2.26/new/sloccount-2.26/sloccount
> --duplicates --wide --details
> /cygdrive/c/workspace/ua_final/DataIntegration/di-core/src/main/ >
> /cygdrive/c/workspace/ua_final/DataIntegration/sloccount.sc
>
> the output of above command is stored in file *sloccount.sc
> * file . PFA
>
> 2: 
> /cygdrive/c/Users/bvcontrolbuild/Downloads/sloccount-2.26/new/sloccount-2.26/sloccount
> /cygdrive/c/workspace/ua_final/DataIntegration/di-core/src/main/ >
> /cygdrive/c/workspace/ua_final/DataIntegration/sloccount.sc
>
> the output of above command is stored in file *sloccount1.sc
> *. PFA
>
> so first thing is , i don't know which command i should go ahead with ?
> second, in Jenkins job configuration , if i put file *sloccount1.sc
> * file , then it does not throw any exception ,
> but, at the end , there is no any report also and no any trend graph also
>
> further, if i put *sloccount.sc * file , then
> jenkins throws follwoing exception at the end of build
>
>
> Started by user Irfan Sayed 
>
> [EnvInject] - Loading node environment variables.
> Building remotely on 10.211.162.150 
>  in workspace 
> C:\workspace\ua_final
> [ua_final] $ cmd /c call 
> C:\Users\BVCONT~1\AppData\Local\Temp\2\hudson4372201469243593858.bat
>
> C:\workspace\ua_final>C:\cygwin64\Cygwin-jenkins.bat
> bash: cannot set terminal process group (-1): Inappropriate ioctl for device
> bash: no job control in this shell
> ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due to 
> exceptionjava.lang.StringIndexOutOfBoundsException 
> :
>  String index out of range: -1
>   at java.lang.String.substring(String.java:1911) 
> 
>   at 
> hudson.plugins.sloccount.model.SloccountReport.extractFolder(SloccountReport.java:71)
>  
> 
>   at 
> hudson.plugins.sloccount.model.SloccountReport.add(SloccountReport.java:49) 
> 
>   at 
> hudson.plugins.sloccount.model.SloccountParser.parseLine(SloccountParser.java:99)
>  
> 
>   at 
> hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:66) 
> 
>   at 
> hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:57) 
> 
>   at 
> hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:47)
>  
> 
>   at 
> hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17)
>  
> 
>   at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2420) 
> 
>   at hudson.remoting.UserRequest.perform(UserRequest.java:118) 
> 
>   at hudson.remoting.UserRequest.perform(UserRequest.java:48) 
> 
>   at hudson.remoting.Request$2.run(Request.java:326) 
> 
>   at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>  
> 
>   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
> 
>   at java.util.concurrent.FutureTask.run(FutureTask.java:166) 
> 

Re: Label restriction issue

2013-11-15 Thread Daniel Beck
This should work.

Open http://yourjenkins/label/LABEL1&&LABEL2&&!NODE_NAME -- which slaves does 
it show to match this expression? Is the one this should not run on listed as 
well?

On 15.11.2013, at 10:06, Thomas  wrote:

> Hi,
> 
> I am encountering an issue with Label restrictions:
> I want a job to be dispatched on a slave node that has labels LABEL1 and 
> LABEL2 but different from NODE_NAME.
> Thus, in the "Restrict where this project can be run", I specified an 
> expression such as:
> LABEL1 && LABEL2 && !NODE_NAME
> 
> but unfortunately, my job starts on NODE_NAME.
> 
> Is there something wrong in my setup or is this an issue with labels ?
> 
> Thanks
> Thomas
> 
> (using jenkins 1.538)
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Label restriction issue

2013-11-15 Thread Thomas
Hi,

I am encountering an issue with Label restrictions:
I want a job to be dispatched on a slave node that has labels LABEL1 and 
LABEL2 but different from NODE_NAME.
Thus, in the "Restrict where this project can be run", I specified an 
expression such as:
LABEL1 && LABEL2 && !NODE_NAME

but unfortunately, my job starts on NODE_NAME.

Is there something wrong in my setup or is this an issue with labels ?

Thanks
Thomas

(using jenkins 1.538)

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.