Re: request on version Jenkins ver. 1.494

[Slide]

If they are showing as red, then they failed somehow. You need to paste
your build log, or look further into it. Jenkins shows a red ball when
_something_ (not necessarily just your build steps) fail during that
project's execution. Without further info (build log, etc) no one here can
help you.


On Wed, Jan 23, 2013 at 12:30 AM, bala nageswar Chadalavada <
baluch...@gmail.com> wrote:

> OK i Enabled AUTO Fresh.
> for example...yesterday Nightly builds are scheduled ran successfully
>
> but it has shown as RED
>
> little confused here
>
> thanks
> bala
>
> On Wed, Jan 23, 2013 at 12:55 PM, Slide  wrote:
>
>> I understand your request and I am telling you that something in the
>> build, whether it is your stuff or something that happens in post-build is
>> failing and making the job be marked as failure. You need to look at your
>> build log and find out why. Otherwise, check to make sure that you have
>> auto-refresh enabled so that if the build occurs it updates the main page.
>>
>>
>> On Wed, Jan 23, 2013 at 12:23 AM, bala nageswar Chadalavada <
>> baluch...@gmail.com> wrote:
>>
>>> My request was..
>>>
>>> Even after the SUCCESSFUL BUILD the main jenkins page showing as RED
>>>
>>> Actual should be BLUE
>>>
>>> On Wed, Jan 23, 2013 at 12:44 PM, Slide  wrote:
>>>
 It sounds like your builds are failing at some point, you need to look
 at the build log and find out why its being marked as a failure.


 On Tue, Jan 22, 2013 at 11:25 PM, bala nageswar Chadalavada <
 baluch...@gmail.com> wrote:

> hI
>
> PLEASE let me know why he builds show red after success ful builds
>
> i am using the Jenkins ver. 1.494 
>
> please suggest further
> --
> Bala.ch
>



 --
 Website: http://earl-of-code.com

>>>
>>>
>>>
>>> --
>>> Bala.ch
>>
>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
>
>
>
> --
> Bala.ch




-- 
Website: http://earl-of-code.com

Re: request on version Jenkins ver. 1.494

[bala nageswar Chadalavada]

OK i Enabled AUTO Fresh.
for example...yesterday Nightly builds are scheduled ran successfully

but it has shown as RED

little confused here

thanks
bala

On Wed, Jan 23, 2013 at 12:55 PM, Slide  wrote:

> I understand your request and I am telling you that something in the
> build, whether it is your stuff or something that happens in post-build is
> failing and making the job be marked as failure. You need to look at your
> build log and find out why. Otherwise, check to make sure that you have
> auto-refresh enabled so that if the build occurs it updates the main page.
>
>
> On Wed, Jan 23, 2013 at 12:23 AM, bala nageswar Chadalavada <
> baluch...@gmail.com> wrote:
>
>> My request was..
>>
>> Even after the SUCCESSFUL BUILD the main jenkins page showing as RED
>>
>> Actual should be BLUE
>>
>> On Wed, Jan 23, 2013 at 12:44 PM, Slide  wrote:
>>
>>> It sounds like your builds are failing at some point, you need to look
>>> at the build log and find out why its being marked as a failure.
>>>
>>>
>>> On Tue, Jan 22, 2013 at 11:25 PM, bala nageswar Chadalavada <
>>> baluch...@gmail.com> wrote:
>>>
 hI

 PLEASE let me know why he builds show red after success ful builds

 i am using the Jenkins ver. 1.494 

 please suggest further
 --
 Bala.ch

>>>
>>>
>>>
>>> --
>>> Website: http://earl-of-code.com
>>>
>>
>>
>>
>> --
>> Bala.ch
>
>
>
>
> --
> Website: http://earl-of-code.com
>



-- 
Bala.ch

Re: request on version Jenkins ver. 1.494

[Slide]

I understand your request and I am telling you that something in the build,
whether it is your stuff or something that happens in post-build is failing
and making the job be marked as failure. You need to look at your build log
and find out why. Otherwise, check to make sure that you have auto-refresh
enabled so that if the build occurs it updates the main page.


On Wed, Jan 23, 2013 at 12:23 AM, bala nageswar Chadalavada <
baluch...@gmail.com> wrote:

> My request was..
>
> Even after the SUCCESSFUL BUILD the main jenkins page showing as RED
>
> Actual should be BLUE
>
> On Wed, Jan 23, 2013 at 12:44 PM, Slide  wrote:
>
>> It sounds like your builds are failing at some point, you need to look at
>> the build log and find out why its being marked as a failure.
>>
>>
>> On Tue, Jan 22, 2013 at 11:25 PM, bala nageswar Chadalavada <
>> baluch...@gmail.com> wrote:
>>
>>> hI
>>>
>>> PLEASE let me know why he builds show red after success ful builds
>>>
>>> i am using the Jenkins ver. 1.494 
>>>
>>> please suggest further
>>> --
>>> Bala.ch
>>>
>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
>
>
>
> --
> Bala.ch




-- 
Website: http://earl-of-code.com

Re: request on version Jenkins ver. 1.494

[bala nageswar Chadalavada]

My request was..

Even after the SUCCESSFUL BUILD the main jenkins page showing as RED

Actual should be BLUE

On Wed, Jan 23, 2013 at 12:44 PM, Slide  wrote:

> It sounds like your builds are failing at some point, you need to look at
> the build log and find out why its being marked as a failure.
>
>
> On Tue, Jan 22, 2013 at 11:25 PM, bala nageswar Chadalavada <
> baluch...@gmail.com> wrote:
>
>> hI
>>
>> PLEASE let me know why he builds show red after success ful builds
>>
>> i am using the Jenkins ver. 1.494 
>>
>> please suggest further
>> --
>> Bala.ch
>>
>
>
>
> --
> Website: http://earl-of-code.com
>



-- 
Bala.ch

Re: request on version Jenkins ver. 1.494

[Slide]

It sounds like your builds are failing at some point, you need to look at
the build log and find out why its being marked as a failure.


On Tue, Jan 22, 2013 at 11:25 PM, bala nageswar Chadalavada <
baluch...@gmail.com> wrote:

> hI
>
> PLEASE let me know why he builds show red after success ful builds
>
> i am using the Jenkins ver. 1.494 
>
> please suggest further
> --
> Bala.ch
>



-- 
Website: http://earl-of-code.com

Re: disable/enable job config file - quick question

[zw]

Hi Uma

Thanks for responding.
I agree with the answer.

On Tuesday, January 22, 2013 12:04:19 PM UTC-8, uma shankar wrote:
>
> Below parameter gets changes as true/false respectivly when you 
> disable/enable the project.
>
> File location: $JENKINS_HOME/jobs/$JOBNAME/config.xml
>
>   true
>
> On Wednesday, 23 January 2013 00:41:46 UTC+5:30, zw wrote:
>>
>> Hi All
>>
>> What file in Jenkins contains the parameter to enable or disable a job ?
>>
>> Thanks 
>>
>

request on version Jenkins ver. 1.494

[bala nageswar Chadalavada]

hI

PLEASE let me know why he builds show red after success ful builds

i am using the Jenkins ver. 1.494 

please suggest further
-- 
Bala.ch

How to change slave port number on command line to connect to a slave - quick question

[zw]

Hi All


We're not sure why we're getting this error message.

2 Jenkins instances are assigned to different port numbers on slave status port.

What are we doing wrong ?



Slave.jar version: 2.2.1
This is a Unix slave
Slave successfully connected and online
Jan 22, 2013 5:23:44 PM com.youdevise.hudson.slavestatus.SlaveListener call
INFO: Slave-status listener starting
Jan 22, 2013 5:23:44 PM com.youdevise.hudson.slavestatus.SlaveListener$1 run
SEVERE: Could not listen on port
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at 
java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at java.net.ServerSocket.(ServerSocket.java:202)
at java.net.ServerSocket.(ServerSocket.java:114)
at 
com.youdevise.hudson.slavestatus.SocketHTTPListener.waitForConnection(SlaveListener.java:129)
at 
com.youdevise.hudson.slavestatus.SlaveListener$1.run(SlaveListener.java:63)
at com.youdevise.hudson.slavestatus.Daemon.go(Daemon.java:16)
at 
com.youdevise.hudson.slavestatus.SlaveListener.call(SlaveListener.java:83)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:283)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
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:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

Error on connecting with a Windows Slave - quick question

[zw]

Hi All

We have 2 Jenkins instances wanting to connect to the same windows box.
1 Jenkins instance connects fine.
But the error has this below:

Connecting to slave4_windows
ERROR: Unexpected error in launching a slave. 
java.net.UnknownHostException: slave4_windows
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:849)
at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1202)
at java.net.InetAddress.getAllByName0(InetAddress.java:1153)
at java.net.InetAddress.getAllByName(InetAddress.java:1083)
at java.net.InetAddress.getAllByName(InetAddress.java:1019)
at java.net.InetAddress.getByName(InetAddress.java:969)
at 
hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:122)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:194)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)


We double checked and we made sure TCP port for JNLP slave agents for each 
of them is different; one uses  other uses 7778.

What are we doing wrong ?

Thanks

ArrayOutOfBoundsException referencing nonexistant build

[Ian Mckay]

Hi Jenkins CI Users,

We are getting the following error after our build succeeds. We only have 7 
builds in the project where it last occured and the exact same error occurs 
across multiple projects. Are there places I can look to see where this #49 
comes from?

[JENKINS] Archiving disabled
Waiting for Jenkins to finish collecting data
ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-us...@googlegroups.comjava.lang.ArrayIndexOutOfBoundsException 
:
 Assertion error: failing to load #49 DESC: lo=2,hi=0,size=20,size2=20
at 
jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:418)
 

at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207) 

at 
hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349) 

at hudson.model.Run.onLoad(Run.java:315) 

at hudson.model.RunMap.retrieve(RunMap.java:226) 

at hudson.model.RunMap.retrieve(RunMap.java:59) 

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:642) 

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:625) 

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432)
 

at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207) 

at 
hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349) 

at hudson.model.Run.onLoad(Run.java:315) 

at hudson.model.RunMap.retrieve(RunMap.java:226) 

at hudson.model.RunMap.retrieve(RunMap.java:59) 

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:642) 

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:625) 

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432)
 

at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207) 

at 
hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349) 

at hudson.model.Run.onLoad(Run.java:315) 

at hudson.model.RunMap.retrieve(RunMap.java:226) 

at hudson.model.RunMap.retrieve(RunMap.java:59) 

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:642) 

at 
jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:625) 

at 
jenkins.model.

Re: Jenkins console gives "Connection refused" when using :ext: for CVSROOT and CVS_RSH=ssh

[Cynsa Bonorris]

that did the trick! version 2.7 lets you set CVS_RSH as an Advanced option 
under Source Code Management in the job config.

many thanks!  was really butting my head against this.

-cynsa

On Sunday, January 20, 2013 9:10:21 AM UTC-8, michael@gmail.com wrote:
>
> Have you tried updating to a newer version of the CVS plugin? It's got 
> built in support for CVS :ext: connections with key files without having to 
> define environment variables to the host operating system.
>
> Thanks,
> Michael
>
>
> On Saturday, January 12, 2013 1:05:42 AM UTC, Cynsa Bonorris wrote:
>>
>> I'm trying to switch from :pserver: to :ext: and use ssh for secure 
>> checkouts. I've set up my keys and am connecting just fine with no password 
>> to the cvs server as my Jenkins/cvs user (builder).
>>
>> However, Jenkins is giving me the following error on checkout, though 
>> when I paste the cvs command into a terminal as builder, the checkout 
>> completes just fine.
>>
>> Started by an SCM change
>> Building on master in workspace /var/lib/jenkins/workspace/foo-co-test
>> [foo-co-test] $ cvs -Q -z3 -d :ext:builder:/cvsrepo/bmi co -P -r 
>> foo-branch -f configuration 
>> XX: Connection refused
>> cvs [checkout aborted]: end of file from server (consult above messages if 
>> any)
>> FATAL: CVS failed. exit code=1
>>
>>
>> (I've obscured our cvs server info in the above.) 
>>
>>
>> in my Jenkins master Global Properties I have the envar CVS_RSH with the 
>> value /usr/bin/ssh
>>
>> but when I use groovyscript to display the envars, I don't see CVS_RSH 
>> populated:
>>
>>
>> TERM=xterm-256color
>> SHELL=/bin/bash
>> SHLVL=3
>> XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
>> PATH=/sbin:/usr/sbin:/bin:/usr/bin
>> USER=builder
>> PWD=/
>> HOME=/build/buildsystem
>> LOGNAME=builder
>> _=/usr/bin/java
>> NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat
>> LD_LIBRARY_PATH=/usr/java/jdk1.6.0_27/jre/lib/i386/server:/usr/java/jdk1.6.0_27/jre/lib/i386:/usr/java/jdk1.6.0_27/jre/../lib/i386
>> LANG=en_US.UTF-8
>> Result: {TERM=xterm-256color, SHELL=/bin/bash, SHLVL=3, 
>> XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, 
>> PATH=/sbin:/usr/sbin:/bin:/usr/bin, USER=builder, PWD=/, 
>> HOME=/build/buildsystem, LOGNAME=builder, _=/usr/bin/java, 
>> NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, 
>> LD_LIBRARY_PATH=/usr/java/jdk1.6.0_27/jre/lib/i386/server:/usr/java/jdk1.6.0_27/jre/lib/i386:/usr/java/jdk1.6.0_27/jre/../lib/i386,
>>  LANG=en_US.UTF-8}
>>
>>
>> any assistance would be appreciated. how do I force Jenkins to export the 
>> CVS_RSH envar? I think that might be the problem, if groovyscript output is 
>> to be believed.
>>
>>
>> -cynsa
>>
>>

Re: Jenkins exit code 143 - due to Unexpected termination of the channel

[BobTheBuilder]

Hello,

Given the significant variation in time range that the JBehave test runs, I
wouldn't expect the problem to be file size.  If it was, it would fail
around the same spot.  However wanting to investigate all possibilities, I
ran a "ulimit -a" and here's what I came up with:
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 106496
max locked memory   (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files  (-n) 4096
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 10240
cpu time   (seconds, -t) unlimited
max user processes  (-u) 106496
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited

Earlier in the day, I pulled down the heap dump from the master. 
Unfortunately it was over 770 megs and I don't have an editor capable of
opening a file that large (my laptop is Windows).  I'm in the process of
requesting some different text editing software.  Given the possibility of
the heap dump containing confidential information, I'm not posting it to the
site.  When I'm able to view the output then I'll worry about it.  :)



--
View this message in context: 
http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347p4652500.html
Sent from the Jenkins users mailing list archive at Nabble.com.

Re: assignedNode in config.xml

[J Arrizza]

Richard,

Thanks for the reply...

I use the "#{@hosturl}/job/#{jobname}/config.xml" url which does not
require a reload of the config file. That is mentioned in the Jenkins doc
page and in google hits .

And I do have other settings working just fine (for example "Block build
when upstream project is building").  Note also that the assignedNode does
work fine if the xml element exists and all my script is doing is changing
the value.

I do this:

- I run the script
- I go to the Jenkins web page in a browser and refresh the page
- the value (or checkbox or whatever) changes to the new value

In short, it's unlikely a caching problem or I'd see problems elsewhere.
This element is part of native Jenkins so no plugin is involved.

Also an update: I fixed my script to always put the newline in there. So
when my Jenkins adds the node it looks like this:

 
http://cm5/hg/sandbox/v01.0/int

false

  http://cm5/hg/sandbox/v01.0/int/

  
  tm9
  false


and when my script adds the node it looks exactly the same:

 
http://cm5/hg/sandbox/v01.0/int

false

  http://cm5/hg/sandbox/v01.0/int/

  
  tm9
  true



Does anyone know what's going on then?

John


On Tue, Jan 22, 2013 at 3:05 PM, Richard Lavoie wrote:

> It might also depends on the caching added lately to prevent reading too
> much unnecessary information into memory.
>
> Note that I'm not in front of my computer so what I'm saying in this mail
> and the last one are somewhat speculations, but some hints on where to look
> at now to see if you can solve this.
>
> R.
>
> On 2013-01-22, at 17:39, J Arrizza  wrote:
>
> Update:
>
> I tried a quick change:
>   - find the scm node and
>   - insert the assignedNode element after it.
>
> Still no joy.
>
> The only thing left that I can see, is there is a missing "\n" after the
>  when my script inserts the new node:
>
>   tm9
>
> while Jenkins adds the newline:
>
>   tm9
>   
>
> That would imply something very wrong with the XML parser in Jenkins, so
> it seems very unlikely this is the problem... but I thought I'd ask it
> anyway.
>
> John
>
> On Tue, Jan 22, 2013 at 1:56 PM, J Arrizza  wrote:
>
>> Hi,
>>
>> I'm writing some scripts to keep track of and update the nodes my jobs
>> use. I've come across a problem that I can't seem to resolve. This is a
>> rather long post, but I want to make sure I give you the info you need.
>>
>> If the "Restrict where this project can be run" is checked on the web
>> page, a node appears in the config.xml:
>>
>>   
>> http://cm5/hg/sandbox/v01.0/int
>> 
>> false
>> 
>>http://cm5/hg/sandbox/v01.0/int/
>> 
>>   
>>   master
>>   false
>>
>> You can see "assignedNode" sandwiched between the scm and canRoam
>> elements. When you uncheck "Restrict where this project can be run", the
>> element disappears from config.xml.
>>
>> So far, so good.
>>
>> I created a ruby script that gets the xml via the api/config.xml
>> interface. It looks for that node and if it's not found, it adds it (BTW I
>> use nokogiri). But my testing is showing that even if I add the node, the
>> checkbox in the web page doesn't get checked.
>>
>> Here are some notes:
>> - If I check the box on the web page and my script just changes the value
>> in it (e.g. from 'master' to 'tm9' and back again), it works perfectly. I
>> run the script, I refresh the web page, and the new value shows up.
>>
>> - When the script adds assignedNode, it adds it to the end of the xml
>> root element, but no joy:
>>
>>   
>> tm9
>>
>>
>> - I tried adding to the front of the xml root element, with no joy:
>>
>> 
>> 
>>   tm9
>>   desc
>>
>>
>> - When I add the assignedNode, it is actually in the config.xml. After I
>> add it,  update the job via the api/xml, and then do a retrieve using
>> api/xml, the config.xml has the node in it. So Jenkins isn't erasing it or
>> anything like that.
>>
>> - If my node is in the config.xml and I check the box on the web page, it
>> moves to just under the scm node and it all works correctly again.
>>
>> - I have done this for several other nodes, checkboxes, etc. and they are
>> working correctly.
>>
>> - I have done this extensively for Hudson and it's working correctly too.
>> Note that the assignedNode in Hudson is called appointedNode and has a few
>> extra fields in there.
>>
>> So, finally, my question: is the assignedNode element position dependent
>> in the config.xml?
>>
>> John
>>
>>
>>
>>
>>
>

Slow SVN commit from batch step

[Bill Wonch]

Hi everyone -

We're in the process of moving Jenkins jobs from a POC box to a server that 
has been configured for that task.

We have one job that takes a 100 MB file from a network share, and commits 
it to trunk, gets some metadata from another process, then creates a tag 
using that metadata.  On the old box this took 6 minutes or so on average. 
 On the new box it is running upwards of an hour.

Here is the script I am running:

@ECHO OFF
echo # INFO: Checking out tag dir
svn co 
https://subversion/svn/Node1/Deployments/flex/%ENVIRONMENT%/%DOMAIN%/tags/ 
%BUILD_TAG%\tags --username USER --password PASSWORD --depth empty
echo # INFO: Making tag dir
mkdir %BUILD_TAG%\tags\%TAG%
echo # INFO: Copying file to tag folder
copy %BUILD_TAG%\trunk\%FILENAME% %BUILD_TAG%\tags\%TAG%\%FILENAME%
echo # INFO: Adding tag folder and %FILENAME%
svn add %BUILD_TAG%\tags\%TAG%
echo # INFO: Setting properties on %FILENAME%
svn propset CR %LBS% %BUILD_TAG%\tags\%TAG%\%FILENAME%
svn propset REVISION %REVISION% %BUILD_TAG%\tags\%TAG%\%FILENAME%
svn propset REQUESTER %BUILD_USER_ID% %BUILD_TAG%\tags\%TAG%\%FILENAME%
svn commit %BUILD_TAG%\tags  --username USER --password PASSWORD -m 
"JENKINS:  Automated deployment"

echo # INFO: TAG CREATED.  FINAL TAG NAME: %TAG%

Anyone have any ideas about what could be going on here?  I thought it 
might be the version of SVN we were running but I made some changes with no 
apparent benefit.

Thanks!
Bill

Re: assignedNode in config.xml

[Richard Lavoie]

It might also depends on the caching added lately to prevent reading too much 
unnecessary information into memory.

Note that I'm not in front of my computer so what I'm saying in this mail and 
the last one are somewhat speculations, but some hints on where to look at now 
to see if you can solve this.

R.

On 2013-01-22, at 17:39, J Arrizza  wrote:

> Update:
> 
> I tried a quick change: 
>   - find the scm node and 
>   - insert the assignedNode element after it. 
> 
> Still no joy.
> 
> The only thing left that I can see, is there is a missing "\n" after the 
>  when my script inserts the new node:
> 
>   tm9
> 
> while Jenkins adds the newline:
> 
>   tm9
>   
> 
> That would imply something very wrong with the XML parser in Jenkins, so it 
> seems very unlikely this is the problem... but I thought I'd ask it anyway.
> 
> John
> 
> On Tue, Jan 22, 2013 at 1:56 PM, J Arrizza  wrote:
>> Hi,
>> 
>> I'm writing some scripts to keep track of and update the nodes my jobs use. 
>> I've come across a problem that I can't seem to resolve. This is a rather 
>> long post, but I want to make sure I give you the info you need.
>> 
>> If the "Restrict where this project can be run" is checked on the web page, 
>> a node appears in the config.xml:
>> 
>>   
>> http://cm5/hg/sandbox/v01.0/int
>> 
>> false
>> 
>>   http://cm5/hg/sandbox/v01.0/int/
>> 
>>   
>>   master
>>   false
>> 
>> You can see "assignedNode" sandwiched between the scm and canRoam elements. 
>> When you uncheck "Restrict where this project can be run", the element 
>> disappears from config.xml. 
>> 
>> So far, so good.
>> 
>> I created a ruby script that gets the xml via the api/config.xml interface. 
>> It looks for that node and if it's not found, it adds it (BTW I use 
>> nokogiri). But my testing is showing that even if I add the node, the 
>> checkbox in the web page doesn't get checked.
>> 
>> Here are some notes:
>> - If I check the box on the web page and my script just changes the value in 
>> it (e.g. from 'master' to 'tm9' and back again), it works perfectly. I run 
>> the script, I refresh the web page, and the new value shows up. 
>> 
>> - When the script adds assignedNode, it adds it to the end of the xml root 
>> element, but no joy:
>> 
>>   
>> tm9
>> 
>> - I tried adding to the front of the xml root element, with no joy:
>> 
>> 
>>   tm9
>>   desc
>> 
>> - When I add the assignedNode, it is actually in the config.xml. After I add 
>> it,  update the job via the api/xml, and then do a retrieve using api/xml, 
>> the config.xml has the node in it. So Jenkins isn't erasing it or anything 
>> like that.
>> 
>> - If my node is in the config.xml and I check the box on the web page, it 
>> moves to just under the scm node and it all works correctly again.
>> 
>> - I have done this for several other nodes, checkboxes, etc. and they are 
>> working correctly. 
>> 
>> - I have done this extensively for Hudson and it's working correctly too. 
>> Note that the assignedNode in Hudson is called appointedNode and has a few 
>> extra fields in there.
>> 
>> So, finally, my question: is the assignedNode element position dependent in 
>> the config.xml?
>> 
>> John
> 

Re: assignedNode in config.xml

[Richard Lavoie]

it is probably because you need to either reload the config file (I wouldn't do 
it that way), update the Job object in memory of jenkins or update the plugin 
object responsible for that option and behavior.

The config is loaded on start and saved when change are made to the internal 
object from the config page.  It is not reloaded at every step otherwise it 
would be way too slow and unusable. So doing changes to the conf is most likely 
useless.

R.

On 2013-01-22, at 17:39, J Arrizza  wrote:

> Update:
> 
> I tried a quick change: 
>   - find the scm node and 
>   - insert the assignedNode element after it. 
> 
> Still no joy.
> 
> The only thing left that I can see, is there is a missing "\n" after the 
>  when my script inserts the new node:
> 
>   tm9
> 
> while Jenkins adds the newline:
> 
>   tm9
>   
> 
> That would imply something very wrong with the XML parser in Jenkins, so it 
> seems very unlikely this is the problem... but I thought I'd ask it anyway.
> 
> John
> 
> On Tue, Jan 22, 2013 at 1:56 PM, J Arrizza  wrote:
>> Hi,
>> 
>> I'm writing some scripts to keep track of and update the nodes my jobs use. 
>> I've come across a problem that I can't seem to resolve. This is a rather 
>> long post, but I want to make sure I give you the info you need.
>> 
>> If the "Restrict where this project can be run" is checked on the web page, 
>> a node appears in the config.xml:
>> 
>>   
>> http://cm5/hg/sandbox/v01.0/int
>> 
>> false
>> 
>>   http://cm5/hg/sandbox/v01.0/int/
>> 
>>   
>>   master
>>   false
>> 
>> You can see "assignedNode" sandwiched between the scm and canRoam elements. 
>> When you uncheck "Restrict where this project can be run", the element 
>> disappears from config.xml. 
>> 
>> So far, so good.
>> 
>> I created a ruby script that gets the xml via the api/config.xml interface. 
>> It looks for that node and if it's not found, it adds it (BTW I use 
>> nokogiri). But my testing is showing that even if I add the node, the 
>> checkbox in the web page doesn't get checked.
>> 
>> Here are some notes:
>> - If I check the box on the web page and my script just changes the value in 
>> it (e.g. from 'master' to 'tm9' and back again), it works perfectly. I run 
>> the script, I refresh the web page, and the new value shows up. 
>> 
>> - When the script adds assignedNode, it adds it to the end of the xml root 
>> element, but no joy:
>> 
>>   
>> tm9
>> 
>> - I tried adding to the front of the xml root element, with no joy:
>> 
>> 
>>   tm9
>>   desc
>> 
>> - When I add the assignedNode, it is actually in the config.xml. After I add 
>> it,  update the job via the api/xml, and then do a retrieve using api/xml, 
>> the config.xml has the node in it. So Jenkins isn't erasing it or anything 
>> like that.
>> 
>> - If my node is in the config.xml and I check the box on the web page, it 
>> moves to just under the scm node and it all works correctly again.
>> 
>> - I have done this for several other nodes, checkboxes, etc. and they are 
>> working correctly. 
>> 
>> - I have done this extensively for Hudson and it's working correctly too. 
>> Note that the assignedNode in Hudson is called appointedNode and has a few 
>> extra fields in there.
>> 
>> So, finally, my question: is the assignedNode element position dependent in 
>> the config.xml?
>> 
>> John
> 

Re: Is it possible to let the jobs roam in a node cluster?

[Stephen Connolly]

My employers have an enterprise plugin that implements an even load
strategy, whereby unused slaves are preferred to slaves where the project
previously built.

On Monday, 21 January 2013, Jan Seidel wrote:

> Sorry for the late reply.
> I did lose this thread out of sight due to serious workload going on
> here...
> Mike got it right. The jobs will stay in the build queue and wait for a
> machine even if 15 executors on other machines are ready to go.
> The approach Mike suggests is not really feasible. There are 200 jobs
> running on the cluster. It would be insane to set up slaves with 1 or a few
> executors and restrict the jobs. I would never stop to reconfigure as the
> setup changes in a very agile manner.
> And Jenkins is overstressed with too many slaves on one machine. I am
> facing troubles with offline slaves if a machine has 8-10 slaves running.
> The result is that I have to start them manually -.- So more slaves on one
> machine is not the solution. Rather fewer with more executors to make sure
> an executor is available at all times.
> But that is IMHO a bit insane and pretty upsetting to see one or two
> machines drowning in build jobs while the other also could compute for SETI
> as they ain't utilized.
>
> I am now trying to reconfigure the entire job topology to get as many jobs
> of a specific type running on one machine with also comes along with
> restrictions. Still no joy but I may be able to make it a bit more comfy.
>
> Any ideas would still be appreciate though.
>
> Cheers
> Jan
>
> Am Donnerstag, 5. April 2012 11:59:07 UTC+2 schrieb Jan Seidel:
>>
>> Hi there,
>>
>> my question is already stated in the title as you can see :)
>>
>> I know that you can let jobs "roam" in a node cluster but can you let
>> it REALLY ROAM?
>> Jenkins tries to let jobs build on nodes which already have been used
>> for building that particular job.
>> That clutters some build queues while other nodes are picking nose.
>>
>> The idea was probably to preserve disk space. But I don't need that
>> intention. "Unimportant jobs" delete their entire workspace upon
>> finish while the important ones store everything until next run. These
>> important jobs have a separate harddisk with loads of space.
>>
>> I have not only several executors running on each sever but also up to
>> 3 instances of jenkins slaves for better usage of system ressources
>> and to box very special jobs. Each slave instance is located on its
>> own harddisk.
>> That way do the special jobs and the slaves have exclusive access to
>> ressources and the jobs may roam in their very own realm.
>> Sounds a bit weird but works perfect except for this '*%&"%§#
>> preferences to build on the same node that has build the job before.
>>
>> The excessive use of the harddisk slows all the builds in a senseless
>> way as the bus reaches the capacity limit on spikes which happen if
>> several jobs spawn at the same time and updates their workspace while
>> there still are loads of unused ressources available on other machines
>> -.-
>>
>> I see at the moment just one solution: split the cluster into more
>> slaves with less executors and reassign the jobs.
>> But that is counteracting my idea a bit as this turns from performance
>> improvement, scalability and convenient usability to further
>> performance improvement and alleviated administration.
>>
>> Has someone an idea how to remove this preference of Jenkins and
>> simply let the jobs build where most executors are available?
>>
>> Cheers
>> Jan
>
>

Re: assignedNode in config.xml

[J Arrizza]

Update:

I tried a quick change:
  - find the scm node and
  - insert the assignedNode element after it.

Still no joy.

The only thing left that I can see, is there is a missing "\n" after the
 when my script inserts the new node:

  tm9

while Jenkins adds the newline:

  tm9
  

That would imply something very wrong with the XML parser in Jenkins, so it
seems very unlikely this is the problem... but I thought I'd ask it anyway.

John

On Tue, Jan 22, 2013 at 1:56 PM, J Arrizza  wrote:

> Hi,
>
> I'm writing some scripts to keep track of and update the nodes my jobs
> use. I've come across a problem that I can't seem to resolve. This is a
> rather long post, but I want to make sure I give you the info you need.
>
> If the "Restrict where this project can be run" is checked on the web
> page, a node appears in the config.xml:
>
>   
> http://cm5/hg/sandbox/v01.0/int
> 
> false
> 
>   http://cm5/hg/sandbox/v01.0/int/
> 
>   
>   master
>   false
>
> You can see "assignedNode" sandwiched between the scm and canRoam
> elements. When you uncheck "Restrict where this project can be run", the
> element disappears from config.xml.
>
> So far, so good.
>
> I created a ruby script that gets the xml via the api/config.xml
> interface. It looks for that node and if it's not found, it adds it (BTW I
> use nokogiri). But my testing is showing that even if I add the node, the
> checkbox in the web page doesn't get checked.
>
> Here are some notes:
> - If I check the box on the web page and my script just changes the value
> in it (e.g. from 'master' to 'tm9' and back again), it works perfectly. I
> run the script, I refresh the web page, and the new value shows up.
>
> - When the script adds assignedNode, it adds it to the end of the xml root
> element, but no joy:
>
>   
> tm9
>
>
> - I tried adding to the front of the xml root element, with no joy:
>
> 
> 
>   tm9
>   desc
>
>
> - When I add the assignedNode, it is actually in the config.xml. After I
> add it,  update the job via the api/xml, and then do a retrieve using
> api/xml, the config.xml has the node in it. So Jenkins isn't erasing it or
> anything like that.
>
> - If my node is in the config.xml and I check the box on the web page, it
> moves to just under the scm node and it all works correctly again.
>
> - I have done this for several other nodes, checkboxes, etc. and they are
> working correctly.
>
> - I have done this extensively for Hudson and it's working correctly too.
> Note that the assignedNode in Hudson is called appointedNode and has a few
> extra fields in there.
>
> So, finally, my question: is the assignedNode element position dependent
> in the config.xml?
>
> John
>
>
>
>
>

assignedNode in config.xml

[J Arrizza]

Hi,

I'm writing some scripts to keep track of and update the nodes my jobs use.
I've come across a problem that I can't seem to resolve. This is a rather
long post, but I want to make sure I give you the info you need.

If the "Restrict where this project can be run" is checked on the web page,
a node appears in the config.xml:

  
http://cm5/hg/sandbox/v01.0/int

false

  http://cm5/hg/sandbox/v01.0/int/

  
  master
  false

You can see "assignedNode" sandwiched between the scm and canRoam elements.
When you uncheck "Restrict where this project can be run", the
element disappears from config.xml.

So far, so good.

I created a ruby script that gets the xml via the api/config.xml interface.
It looks for that node and if it's not found, it adds it (BTW I use
nokogiri). But my testing is showing that even if I add the node, the
checkbox in the web page doesn't get checked.

Here are some notes:
- If I check the box on the web page and my script just changes the value
in it (e.g. from 'master' to 'tm9' and back again), it works perfectly. I
run the script, I refresh the web page, and the new value shows up.

- When the script adds assignedNode, it adds it to the end of the xml root
element, but no joy:

  
tm9


- I tried adding to the front of the xml root element, with no joy:



  tm9
  desc


- When I add the assignedNode, it is actually in the config.xml. After I
add it,  update the job via the api/xml, and then do a retrieve using
api/xml, the config.xml has the node in it. So Jenkins isn't erasing it or
anything like that.

- If my node is in the config.xml and I check the box on the web page, it
moves to just under the scm node and it all works correctly again.

- I have done this for several other nodes, checkboxes, etc. and they are
working correctly.

- I have done this extensively for Hudson and it's working correctly too.
Note that the assignedNode in Hudson is called appointedNode and has a few
extra fields in there.

So, finally, my question: is the assignedNode element position dependent in
the config.xml?

John

Re: Is it possible to let the jobs roam in a node cluster?

[liam.j.bennett]

I think this subject has come up several times. I know I have suffered with 
it for a long time myself. I can see situations where each method would be 
suitable so we should be able to configure it both globally at the 
label-level. So for example nodes with the label "labelA" have roaming mode 
set to "build on last node" and nodes with label "labelB" have roaming mode 
set to "build on any available". I would suggest this for a plugin but it 
is likely to also require core changes.

On Monday, January 21, 2013 8:01:01 PM UTC, Jan Seidel wrote:
>
> Sorry for the late reply.
> I did lose this thread out of sight due to serious workload going on 
> here...
> Mike got it right. The jobs will stay in the build queue and wait for a 
> machine even if 15 executors on other machines are ready to go.
> The approach Mike suggests is not really feasible. There are 200 jobs 
> running on the cluster. It would be insane to set up slaves with 1 or a few 
> executors and restrict the jobs. I would never stop to reconfigure as the 
> setup changes in a very agile manner.
> And Jenkins is overstressed with too many slaves on one machine. I am 
> facing troubles with offline slaves if a machine has 8-10 slaves running.
> The result is that I have to start them manually -.- So more slaves on one 
> machine is not the solution. Rather fewer with more executors to make sure 
> an executor is available at all times.
> But that is IMHO a bit insane and pretty upsetting to see one or two 
> machines drowning in build jobs while the other also could compute for SETI 
> as they ain't utilized.
>
> I am now trying to reconfigure the entire job topology to get as many jobs 
> of a specific type running on one machine with also comes along with 
> restrictions. Still no joy but I may be able to make it a bit more comfy.
>
> Any ideas would still be appreciate though.
>
> Cheers
> Jan
>
> Am Donnerstag, 5. April 2012 11:59:07 UTC+2 schrieb Jan Seidel:
>>
>> Hi there, 
>>
>> my question is already stated in the title as you can see :) 
>>
>> I know that you can let jobs "roam" in a node cluster but can you let 
>> it REALLY ROAM? 
>> Jenkins tries to let jobs build on nodes which already have been used 
>> for building that particular job. 
>> That clutters some build queues while other nodes are picking nose. 
>>
>> The idea was probably to preserve disk space. But I don't need that 
>> intention. "Unimportant jobs" delete their entire workspace upon 
>> finish while the important ones store everything until next run. These 
>> important jobs have a separate harddisk with loads of space. 
>>
>> I have not only several executors running on each sever but also up to 
>> 3 instances of jenkins slaves for better usage of system ressources 
>> and to box very special jobs. Each slave instance is located on its 
>> own harddisk. 
>> That way do the special jobs and the slaves have exclusive access to 
>> ressources and the jobs may roam in their very own realm. 
>> Sounds a bit weird but works perfect except for this '*%&"%§# 
>> preferences to build on the same node that has build the job before. 
>>
>> The excessive use of the harddisk slows all the builds in a senseless 
>> way as the bus reaches the capacity limit on spikes which happen if 
>> several jobs spawn at the same time and updates their workspace while 
>> there still are loads of unused ressources available on other machines 
>> -.- 
>>
>> I see at the moment just one solution: split the cluster into more 
>> slaves with less executors and reassign the jobs. 
>> But that is counteracting my idea a bit as this turns from performance 
>> improvement, scalability and convenient usability to further 
>> performance improvement and alleviated administration. 
>>
>> Has someone an idea how to remove this preference of Jenkins and 
>> simply let the jobs build where most executors are available? 
>>
>> Cheers 
>> Jan
>
>

Re: disable/enable job config file - quick question

[uma shankar]

Below parameter gets changes as true/false respectivly when you 
disable/enable the project.

File location: $JENKINS_HOME/jobs/$JOBNAME/config.xml

  true

On Wednesday, 23 January 2013 00:41:46 UTC+5:30, zw wrote:
>
> Hi All
>
> What file in Jenkins contains the parameter to enable or disable a job ?
>
> Thanks 
>

Changes since last success in email using email-ext jelly script

[uma shankar]

Hi,

I have been using email-ext plugin bundled script "html.jelly" for email. 
But now i want to add changes since last success in email.

I have tried some code provided here 
"http://stackoverflow.com/questions/6386635/infinite-loop-in-jelly-script-for-jenkins-email-ext-plugin-why";,
 
but getting "JellyException: null:82:63: **Java heap space" error

Jenkins log:

Jan 23, 2013 12:58:13 AM 
hudson.plugins.emailext.plugins.content.JellyScriptContent getContent
SEVERE: null
org.apache.commons.jelly.JellyTagException: null:82:63:  Java heap 
space
at 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65)
at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhileTag.doTag(WhileTag.java:62)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65)
at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
hudson.plugins.emailext.plugins.content.JellyScriptContent.convert(JellyScriptContent.java:126)
at 
hudson.plugins.emailext.plugins.content.JellyScriptContent.renderContent(JellyScriptContent.java:117)
at 
hudson.plugins.emailext.plugins.content.JellyScriptContent.getContent(JellyScriptContent.java:73)
at 
hudson.plugins.emailext.plugins.ContentBuilder.replaceTokensWithContent(ContentBuilder.java:123)
at 
hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:96)
at 
hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:662)
at 
hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:457)
at 
hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:297)
at 
hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289)
at 
hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
at hudson.model.Run.execute(Run.java:1546)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Unknown Source)
at java.io.ByteArrayOutputStream.write(Unknown Source)
at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source)
at sun.nio.cs.StreamEncoder.implFlushBuffer(Unknown Source)
at sun.nio.cs.StreamEncoder.implFlush(Unknown Source)
at sun.nio.cs.StreamEncoder.flush(Unknown Source)
at java.io.OutputStreamWriter.flush(Unknown Source)
at java.io.BufferedWriter.flush(Unknown Source)
at org.dom4j.io.XMLWriter.flush(XMLWriter.java:276)
at org.apache.commons.jelly.XMLOutput.flush(XMLOutput.java:127)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:271)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65)
at 
org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.

Re: Converting paths with spaces

[Jonathan Rogers]

Benjamin Lau wrote:
> command.com changed to cmd.exe at some point in the last decade or
> two... maybe that's an NT and later thing...
>

Actually, they coexisted for a long time. NT did add cmd.exe as a native
program but continued to include command.com for backward compatibility.
Not surprisingly given the names, command.com is a 16-bit real mode DOS
program and cmd.exe is a protected mode Win32 one. They understand a
similar language, though cmd.exe extended it some. It seems that in
recent years, 64-bit versions of Windows have finally dropped command.com.

-- 
Jonathan Rogers

jenkins clustering

[Matteo]

Hello,

first i'd like to thank developers for this great project.

I'm sorry if already asked but i'm new on this list and searching the web
has produced no results.

We have a jenkins installation with 1 master and 5 slaves connected through 
ssh.

We are mostly a java shop and jenkins is central to our infrastructure 
since we
build and deploy releases to servers from it.

For this reason slave resiliency in the face of master failure is paramount 
to us.

My question:
Is there a way, in a master/slave configuration, to have slave builds
running to completion even in case of master failure (ideally refetching
console logs once the master is back up :))?

In our current setup, we get a proxy error on master UI and builds are 
aborted.

Thanks in advance for any hint,

-m

disable/enable job config file - quick question

[zw]

Hi All

What file in Jenkins contains the parameter to enable or disable a job ?

Thanks 

Re: Amazon EC2 plugin not waking up stopped slaves

[KEVIN FLEMING (BLOOMBERG/ 731 LEXIN)]

(Please use 'reply' and not 'reply-all'... I don't need two copies of your 
replies, one in my inbox )

As I mentioned before, instance cap management in the current ec2-plugin is a 
bit suspect, although I would have only expected it to fail in the other 
direction (too many instances, not too few).



- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
Cc: KEVIN FLEMING (BLOOMBERG/ 731 LEXIN)
At: Jan 22 2013 12:53:05

Ok.

Rebooted the box and it now works.

I tried increasing the caps - did not work
reload jenkins-ci - did not work
reboot, so restart jenkins - worked

Cap value must only being read at startup time then.

Will have to find time to full test this, and get into the jenkins bug 
tracker.

Anyway thank for the replies.

On Tuesday, January 22, 2013 4:28:28 PM UTC, Kevin Fleming wrote:
>
>  Yes, I have a global instance cap and also a cap on each slave template 
> (although per-template caps don't work properly in the current ec2-plugin 
> version... I have patches to fix that that I'll be submitting soon). I 
> believe I saw proper resumption of stopped instances even before I fixed 
> the instance cap handling though.
>
> You may be running into another bug in the ec2-plugin though, for which I 
> also have a fix but it requires Jenkins core changes. When you see a new 
> instance getting spawned unnecessarily, is the stopped instance *also* 
> resumed but left idle?
>
> --
> *From:*jdra...@nationaltheatre.org.uk *To:*
> jenkins...@googlegroups.com *Cc:*KEVIN FLEMING (BLOOMBERG/ 
> 731 LEXIN)*Date:* 1/22 11:25
> --
>
>  Hi, thanks for the reply.
>
> In your settings do you have a cap on the number of instance you can 
> launch?
>
> Otherwise I am not sure what's wrong since it a very basic setup and 
> there's little in the logs to go on.
>
> On Tuesday, January 22, 2013 2:47:56 PM UTC, Kevin Fleming wrote:
>>
>>  Yes, I use it heavily with my slave templates configured to 'stop' 
>> instead of 'terminate', and the plugin properly restarts the slaves when 
>> they are needed.
>>
>> --
>> *From:*jenkins...@googlegroups.com*To:*jenkins...@googlegroups.com*Date:* 
>> 1/20 
>> 8:57
>> --
>>
>>  Hi, would log this as a bug but I can't login to jenkins jria (ldap 
>> error).
>>
>> The plugin seems to work fine apart from automatically waking up a slave 
>> which is stopped.
>>
>> Logs say it want to provision another node, but it should wake up the 
>> stopped node and use that.
>>
>> If I go to the node page and start the slave it comes up fine and the job 
>> runs.
>>
>> Jenkins - 1.480.2 LTS
>> Amazon EC2 
>> plugin - 
>> 1.17
>> Master with no executors, set to no be used
>> 1 slave and can only provision 1 aws node
>>
>> Anybody use this plugin, with stopped instead of terminate?
>>
>> Any help would be great.
>>
>

Re: Converting paths with spaces

[Benjamin Lau]

command.com changed to cmd.exe at some point in the last decade or
two... maybe that's an NT and later thing...

Ben

On Tue, Jan 22, 2013 at 1:02 PM, Scott Evans  wrote:
> Slide,
>
> Yes, that would do pretty much what I needed, if I weren't needing to run
> this on a Win-7 x64 box which doesn't have command.com on it.  In any event,
> since my original email, we've decided that since it's a "bad thing" to have
> spaces in project names (especially when we're multi-os), that it will just
> be a requirement that projects which use this legacy tool can't have spaces
> in their project names, so the workspaces will not have spaces in them
> either.
>
> Thanks to everyone for their contributions to this topic.
>
> Scott
>
>
> On Tue, Jan 22, 2013 at 10:22 AM, Slide  wrote:
>>
>> Is [1] what you are looking for?
>>
>> slide
>>
>> 1 -
>> http://www.andypemberton.com/engineering/windows-short-file-name-shortpath-in-ant-task/
>>
>>
>> On Tue, Jan 22, 2013 at 9:19 AM, JonathanRRogers
>>  wrote:
>>>
>>> On Tuesday, January 22, 2013 10:54:40 AM UTC-5, SA Evans wrote:

 Within my ant build script, I have a legacy program that is failing
 because the workspace name has a space in it, and so it's failing as the
 whole path isn't getting passed in as an argument to this program.  It
 really isn't a solution at this time to change the project name to one
 without spaces, so I'm wondering if anyone has any quick/dirty suggestions
 on how to convert, within Ant, a path which has spaces in it into an 8.3
 type path.

>>>
>>> This is most likely a problem related to insufficient quoting of a
>>> command or path. I doubt an "8.3 type path" is really what you need.
>>
>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>
>

Re: Converting paths with spaces

[Scott Evans]

Slide,

Yes, that would do pretty much what I needed, if I weren't needing to run
this on a Win-7 x64 box which doesn't have command.com on it.  In any
event, since my original email, we've decided that since it's a "bad thing"
to have spaces in project names (especially when we're multi-os), that it
will just be a requirement that projects which use this legacy tool can't
have spaces in their project names, so the workspaces will not have spaces
in them either.

Thanks to everyone for their contributions to this topic.

Scott

On Tue, Jan 22, 2013 at 10:22 AM, Slide  wrote:

> Is [1] what you are looking for?
>
> slide
>
> 1 -
> http://www.andypemberton.com/engineering/windows-short-file-name-shortpath-in-ant-task/
>
>
> On Tue, Jan 22, 2013 at 9:19 AM, JonathanRRogers <
> jonathanrrog...@gmail.com> wrote:
>
>> On Tuesday, January 22, 2013 10:54:40 AM UTC-5, SA Evans wrote:
>>>
>>> Within my ant build script, I have a legacy program that is failing
>>> because the workspace name has a space in it, and so it's failing as the
>>> whole path isn't getting passed in as an argument to this program.  It
>>> really isn't a solution at this time to change the project name to one
>>> without spaces, so I'm wondering if anyone has any quick/dirty suggestions
>>> on how to convert, within Ant, a path which has spaces in it into an 8.3
>>> type path.
>>>
>>>
>> This is most likely a problem related to insufficient quoting of a
>> command or path. I doubt an "8.3 type path" is really what you need.
>>
>
>
>
> --
> Website: http://earl-of-code.com
>

Re: Amazon EC2 plugin not waking up stopped slaves

[jpd4nt]

Ok.

Rebooted the box and it now works.

I tried increasing the caps - did not work
reload jenkins-ci - did not work
reboot, so restart jenkins - worked

Cap value must only being read at startup time then.

Will have to find time to full test this, and get into the jenkins bug 
tracker.

Anyway thank for the replies.

On Tuesday, January 22, 2013 4:28:28 PM UTC, Kevin Fleming wrote:
>
>  Yes, I have a global instance cap and also a cap on each slave template 
> (although per-template caps don't work properly in the current ec2-plugin 
> version... I have patches to fix that that I'll be submitting soon). I 
> believe I saw proper resumption of stopped instances even before I fixed 
> the instance cap handling though.
>
> You may be running into another bug in the ec2-plugin though, for which I 
> also have a fix but it requires Jenkins core changes. When you see a new 
> instance getting spawned unnecessarily, is the stopped instance *also* 
> resumed but left idle?
>
> --
> *From:*jdra...@nationaltheatre.org.uk *To:*
> jenkins...@googlegroups.com *Cc:*KEVIN FLEMING (BLOOMBERG/ 
> 731 LEXIN)*Date:* 1/22 11:25
> --
>
>  Hi, thanks for the reply.
>
> In your settings do you have a cap on the number of instance you can 
> launch?
>
> Otherwise I am not sure what's wrong since it a very basic setup and 
> there's little in the logs to go on.
>
> On Tuesday, January 22, 2013 2:47:56 PM UTC, Kevin Fleming wrote:
>>
>>  Yes, I use it heavily with my slave templates configured to 'stop' 
>> instead of 'terminate', and the plugin properly restarts the slaves when 
>> they are needed.
>>
>> --
>> *From:*jenkins...@googlegroups.com*To:*jenkins...@googlegroups.com*Date:* 
>> 1/20 
>> 8:57
>> --
>>
>>  Hi, would log this as a bug but I can't login to jenkins jria (ldap 
>> error).
>>
>> The plugin seems to work fine apart from automatically waking up a slave 
>> which is stopped.
>>
>> Logs say it want to provision another node, but it should wake up the 
>> stopped node and use that.
>>
>> If I go to the node page and start the slave it comes up fine and the job 
>> runs.
>>
>> Jenkins - 1.480.2 LTS
>> Amazon EC2 
>> plugin - 
>> 1.17
>> Master with no executors, set to no be used
>> 1 slave and can only provision 1 aws node
>>
>> Anybody use this plugin, with stopped instead of terminate?
>>
>> Any help would be great.
>>
>

FATAL: command execution failed.Maybe you need to configure the job to choose one of your Phing installations?

[Vishal Mote]

Started by user anonymous 
Building in workspace /var/lib/jenkins/jobs/MyJob1/workspace
looking for '/var/lib/jenkins/jobs/MyJob1/workspace/build.xml' ... 
use '/var/lib/jenkins/jobs/MyJob1/workspace' as a working directory. 
[workspace] $ phing -buildfile /var/lib/jenkins/jobs/MyJob1/workspace/build.xml 
-logger phing.listener.DefaultLogger
FATAL: command execution failed.Maybe you need to configure the job to choose 
one of your Phing installations?java.io.IOException 
: Cannot run 
program "phing" (in directory "/var/lib/jenkins/jobs/MyJob1/workspace"): 
error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) 

at hudson.Proc$LocalProc.(Proc.java:244) 

at hudson.Proc$LocalProc.(Proc.java:216) 

at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) 

at hudson.Launcher$ProcStarter.start(Launcher.java:338) 

at hudson.Launcher$ProcStarter.join(Launcher.java:345) 

at hudson.plugins.phing.PhingBuilder.perform(PhingBuilder.java:195) 

at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 

at 
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) 

at hudson.model.Build$RunnerImpl.build(Build.java:178) 

at hudson.model.Build$RunnerImpl.doRun(Build.java:139) 

at 
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) 

at hudson.model.Run.run(Run.java:1438) 

at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 

at hudson.model.ResourceController.execute(ResourceController.java:88) 

at hudson.model.Executor.run(Executor.java:239) 

Caused by: java.io.IOException 
: error=2, 
No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:135)
at java.lang.ProcessImpl.start(ProcessImpl.java:130)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021)
... 15 more
Build step 'Invoke Phing targets' marked build as failure
Finished: FAILURE















I have installed only one installation of phing. even i told it to choose which 
installation to select its giving following error.






Started by user anonymous 
Building in workspace /var/lib/jenkins/jobs/MyJob1/workspace
looking for '/var/lib/jenkins/jobs/MyJob1/workspace/build.xml' ... 
use '/var/lib/jenkins/jobs/MyJob1/workspace' as a working directory. 
[workspace] $ -buildfile /var/lib/jenkins/jobs/MyJob1/workspace/build.xml 
-logger phing.listener.DefaultLogger
FATAL: command execution failed.java.io.IOException 
: Cannot run 
program "-buildfile" (in directory "/var/lib/jenkins/jobs/MyJob1/workspace"): 
error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) 

at hudson.Proc$LocalProc.(Proc.java:244) 

at hudson.Proc$LocalProc.(Proc.java:216) 

Re: PHING_HOME VS PEAR

[Vishal Mote]

Started by user anonymous 
Building in workspace /var/lib/jenkins/jobs/MyJob1/workspace
looking for '/var/lib/jenkins/jobs/MyJob1/workspace/build.xml' ... 
use '/var/lib/jenkins/jobs/MyJob1/workspace' as a working directory. 
[workspace] $ phing -buildfile /var/lib/jenkins/jobs/MyJob1/workspace/build.xml 
-logger phing.listener.DefaultLogger
FATAL: command execution failed.Maybe you need to configure the job to choose 
one of your Phing installations?java.io.IOException 
: Cannot run 
program "phing" (in directory "/var/lib/jenkins/jobs/MyJob1/workspace"): 
error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) 

at hudson.Proc$LocalProc.(Proc.java:244) 

at hudson.Proc$LocalProc.(Proc.java:216) 

at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) 

at hudson.Launcher$ProcStarter.start(Launcher.java:338) 

at hudson.Launcher$ProcStarter.join(Launcher.java:345) 

at hudson.plugins.phing.PhingBuilder.perform(PhingBuilder.java:195) 

at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 

at 
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) 

at hudson.model.Build$RunnerImpl.build(Build.java:178) 

at hudson.model.Build$RunnerImpl.doRun(Build.java:139) 

at 
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) 

at hudson.model.Run.run(Run.java:1438) 

at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 

at hudson.model.ResourceController.execute(ResourceController.java:88) 

at hudson.model.Executor.run(Executor.java:239) 

Caused by: java.io.IOException 
: error=2, 
No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:135)
at java.lang.ProcessImpl.start(ProcessImpl.java:130)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021)
... 15 more
Build step 'Invoke Phing targets' marked build as failure
Finished: FAILURE



How can I solve this problem





On Wednesday, October 12, 2011 1:58:32 PM UTC+5:30, llaumgui wrote:
>
> Thk, in fact, I must no enter any information for phing.

Re: infrastructure chef and jenkins integration usage - quick question

[Brad Knowles]

On Jan 22, 2013, at 11:21 AM, zw  wrote:

> Could experts here share how infrastructure chef is usually used with jenkins 
> ?
> Is chef, which we believe are meant for configurations and deployments to 
> different environments, integrated with Jenkins using the execute shell step ?

It depends on what you need to automate.  You could use Jenkins to 
automatically kick off chef deployments in various environments, depending on 
whether certain criteria have been fulfilled -- for example, perhaps you have 
an updated code base that passes all the unit tests, integration tests, and 
regression tests, and so now you need to push it out to your Staging 
environment so that you can do load testing.

You could also use Chef to automate deployment of Jenkins servers, or perhaps 
just the slaves.

They are both very flexible tools, and they can interface in a variety of ways.

> We new to chef.

Note that Opscode also has a mailing list for their user base, see 
.

--
Brad Knowles 
LinkedIn Profile: 

Re: Amazon EC2 plugin not waking up stopped slaves

[jpd4nt]

The stopped instance is left in the stopped state.

It just throws: Instance cap reached, not provisioning.

I have set the global cap to 10, slave tmpl to 10 so it should spawn 10 
slaves.



On Tuesday, January 22, 2013 4:28:28 PM UTC, Kevin Fleming wrote:
>
>  Yes, I have a global instance cap and also a cap on each slave template 
> (although per-template caps don't work properly in the current ec2-plugin 
> version... I have patches to fix that that I'll be submitting soon). I 
> believe I saw proper resumption of stopped instances even before I fixed 
> the instance cap handling though.
>
> You may be running into another bug in the ec2-plugin though, for which I 
> also have a fix but it requires Jenkins core changes. When you see a new 
> instance getting spawned unnecessarily, is the stopped instance *also* 
> resumed but left idle?
>
> --
> *From:*jdra...@nationaltheatre.org.uk *To:*
> jenkins...@googlegroups.com *Cc:*KEVIN FLEMING (BLOOMBERG/ 
> 731 LEXIN)*Date:* 1/22 11:25
> --
>
>  Hi, thanks for the reply.
>
> In your settings do you have a cap on the number of instance you can 
> launch?
>
> Otherwise I am not sure what's wrong since it a very basic setup and 
> there's little in the logs to go on.
>
> On Tuesday, January 22, 2013 2:47:56 PM UTC, Kevin Fleming wrote:
>>
>>  Yes, I use it heavily with my slave templates configured to 'stop' 
>> instead of 'terminate', and the plugin properly restarts the slaves when 
>> they are needed.
>>
>> --
>> *From:*jenkins...@googlegroups.com*To:*jenkins...@googlegroups.com*Date:* 
>> 1/20 
>> 8:57
>> --
>>
>>  Hi, would log this as a bug but I can't login to jenkins jria (ldap 
>> error).
>>
>> The plugin seems to work fine apart from automatically waking up a slave 
>> which is stopped.
>>
>> Logs say it want to provision another node, but it should wake up the 
>> stopped node and use that.
>>
>> If I go to the node page and start the slave it comes up fine and the job 
>> runs.
>>
>> Jenkins - 1.480.2 LTS
>> Amazon EC2 
>> plugin - 
>> 1.17
>> Master with no executors, set to no be used
>> 1 slave and can only provision 1 aws node
>>
>> Anybody use this plugin, with stopped instead of terminate?
>>
>> Any help would be great.
>>
>

infrastructure chef and jenkins integration usage - quick question

[zw]

Hi

Could experts here share how infrastructure chef is usually used with 
jenkins ?
Is chef, which we believe are meant for configurations and deployments to 
different environments, integrated with Jenkins using the execute shell 
step ?

We new to chef.

Re: Amazon EC2 plugin not waking up stopped slaves

[KEVIN FLEMING (BLOOMBERG/ 731 LEXIN)]

Yes, I have a global instance cap and also a cap on each slave template 
(although per-template caps don't work properly in the current ec2-plugin 
version... I have patches to fix that that I'll be submitting soon). I believe 
I saw proper resumption of stopped instances even before I fixed the instance 
cap handling though.

You may be running into another bug in the ec2-plugin though, for which I also 
have a fix but it requires Jenkins core changes. When you see a new instance 
getting spawned unnecessarily, is the stopped instance *also* resumed but left 
idle?



- Original Message -
From: jdrawn...@nationaltheatre.org.uk
To: jenkinsci-users@googlegroups.com
Cc: KEVIN FLEMING (BLOOMBERG/ 731 LEXIN)
At: Jan 22 2013 11:25:22

Hi, thanks for the reply.

In your settings do you have a cap on the number of instance you can launch?

Otherwise I am not sure what's wrong since it a very basic setup and 
there's little in the logs to go on.

On Tuesday, January 22, 2013 2:47:56 PM UTC, Kevin Fleming wrote:
>
>  Yes, I use it heavily with my slave templates configured to 'stop' 
> instead of 'terminate', and the plugin properly restarts the slaves when 
> they are needed.
>
> --
> *From:*jenkins...@googlegroups.com *To:*
> jenkins...@googlegroups.com *Date:* 1/20 8:57
> --
>
>  Hi, would log this as a bug but I can't login to jenkins jria (ldap 
> error).
>
> The plugin seems to work fine apart from automatically waking up a slave 
> which is stopped.
>
> Logs say it want to provision another node, but it should wake up the 
> stopped node and use that.
>
> If I go to the node page and start the slave it comes up fine and the job 
> runs.
>
> Jenkins - 1.480.2 LTS
> Amazon EC2 
> plugin - 
> 1.17
> Master with no executors, set to no be used
> 1 slave and can only provision 1 aws node
>
> Anybody use this plugin, with stopped instead of terminate?
>
> Any help would be great.
>

RE: Converting paths with spaces

[Todd Greer]

8.3 conversion still exists in Windows 8, at least in cmd.exe (I tested it). I 
googled "find 8.3 folder name" and found 
http://stackoverflow.com/questions/1333589/how-do-i-transform-the-working-directory-into-a-8-3-short-file-name-using-batch,
 which provides what appears to be an excellent answer if you're willing to 
hand the work to a batch script. If for some reason it doesn't work, you could 
also just hard code the altered path.

--
Todd

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mandeville, Rob
Sent: Tuesday, January 22, 2013 10:10 AM
To: 'jenkinsci-users@googlegroups.com'
Subject: RE: Converting paths with spaces

You mean like C:\PROGRA~1?  I don't think 8.3 conversion exists any more.  I 
think it went out with Windows 95.

Can you surround the argument with double-quotes?

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Scott Evans
Sent: Tuesday, January 22, 2013 10:55 AM
To: jenkinsci-users@googlegroups.com
Subject: Converting paths with spaces

Within my ant build script, I have a legacy program that is failing because the 
workspace name has a space in it, and so it's failing as the whole path isn't 
getting passed in as an argument to this program.  It really isn't a solution 
at this time to change the project name to one without spaces, so I'm wondering 
if anyone has any quick/dirty suggestions on how to convert, within Ant, a path 
which has spaces in it into an 8.3 type path.

Thanks!
Scott
The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

Re: Converting paths with spaces

[Jonathan Rogers]

Slide wrote:
> Is [1] what you are looking for?
>
> slide
>
> 1
> - 
> http://www.andypemberton.com/engineering/windows-short-file-name-shortpath-in-ant-task/
>
I should have known better than to reply to a question about Windows
brain damage.

-- 
Jonathan Rogers

Re: Amazon EC2 plugin not waking up stopped slaves

[jpd4nt]

Hi, thanks for the reply.

In your settings do you have a cap on the number of instance you can launch?

Otherwise I am not sure what's wrong since it a very basic setup and 
there's little in the logs to go on.

On Tuesday, January 22, 2013 2:47:56 PM UTC, Kevin Fleming wrote:
>
>  Yes, I use it heavily with my slave templates configured to 'stop' 
> instead of 'terminate', and the plugin properly restarts the slaves when 
> they are needed.
>
> --
> *From:*jenkins...@googlegroups.com *To:*
> jenkins...@googlegroups.com *Date:* 1/20 8:57
> --
>
>  Hi, would log this as a bug but I can't login to jenkins jria (ldap 
> error).
>
> The plugin seems to work fine apart from automatically waking up a slave 
> which is stopped.
>
> Logs say it want to provision another node, but it should wake up the 
> stopped node and use that.
>
> If I go to the node page and start the slave it comes up fine and the job 
> runs.
>
> Jenkins - 1.480.2 LTS
> Amazon EC2 
> plugin - 
> 1.17
> Master with no executors, set to no be used
> 1 slave and can only provision 1 aws node
>
> Anybody use this plugin, with stopped instead of terminate?
>
> Any help would be great.
>

Re: Converting paths with spaces

[Slide]

Is [1] what you are looking for?

slide

1 -
http://www.andypemberton.com/engineering/windows-short-file-name-shortpath-in-ant-task/


On Tue, Jan 22, 2013 at 9:19 AM, JonathanRRogers
wrote:

> On Tuesday, January 22, 2013 10:54:40 AM UTC-5, SA Evans wrote:
>>
>> Within my ant build script, I have a legacy program that is failing
>> because the workspace name has a space in it, and so it's failing as the
>> whole path isn't getting passed in as an argument to this program.  It
>> really isn't a solution at this time to change the project name to one
>> without spaces, so I'm wondering if anyone has any quick/dirty suggestions
>> on how to convert, within Ant, a path which has spaces in it into an 8.3
>> type path.
>>
>>
> This is most likely a problem related to insufficient quoting of a command
> or path. I doubt an "8.3 type path" is really what you need.
>



-- 
Website: http://earl-of-code.com

Re: Converting paths with spaces

[JonathanRRogers]

On Tuesday, January 22, 2013 10:54:40 AM UTC-5, SA Evans wrote:
>
> Within my ant build script, I have a legacy program that is failing 
> because the workspace name has a space in it, and so it's failing as the 
> whole path isn't getting passed in as an argument to this program.  It 
> really isn't a solution at this time to change the project name to one 
> without spaces, so I'm wondering if anyone has any quick/dirty suggestions 
> on how to convert, within Ant, a path which has spaces in it into an 8.3 
> type path.
>
>
This is most likely a problem related to insufficient quoting of a command 
or path. I doubt an "8.3 type path" is really what you need.

RE: Converting paths with spaces

[Mandeville, Rob]

You mean like C:\PROGRA~1?  I don't think 8.3 conversion exists any more.  I 
think it went out with Windows 95.

Can you surround the argument with double-quotes?

--Rob

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Scott Evans
Sent: Tuesday, January 22, 2013 10:55 AM
To: jenkinsci-users@googlegroups.com
Subject: Converting paths with spaces

Within my ant build script, I have a legacy program that is failing because the 
workspace name has a space in it, and so it's failing as the whole path isn't 
getting passed in as an argument to this program.  It really isn't a solution 
at this time to change the project name to one without spaces, so I'm wondering 
if anyone has any quick/dirty suggestions on how to convert, within Ant, a path 
which has spaces in it into an 8.3 type path.

Thanks!
Scott

The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

Converting paths with spaces

[Scott Evans]

Within my ant build script, I have a legacy program that is failing because
the workspace name has a space in it, and so it's failing as the whole path
isn't getting passed in as an argument to this program.  It really isn't a
solution at this time to change the project name to one without spaces, so
I'm wondering if anyone has any quick/dirty suggestions on how to convert,
within Ant, a path which has spaces in it into an 8.3 type path.

Thanks!
Scott

Re: Job Queue and parallel batch commands

[Eric Pyle]

Hi Fabian,

1. The simplest solution would be to restrict those "similar" jobs to a 
single slave, and set up that slave with only 1 executor.


2. There's no way to do this as far as I know. You could achieve 
something similar if you set up each batch command in a separate job and 
used the Join plugin to manage them from a single job to start all and 
another single job to run after all batch command jobs are done.


Regards,
Eric

On 1/22/2013 8:23 AM, Fabian Birk wrote:

Hello,

I have 2 questions:

1. Is it possible to set up a queue for similar jobs? I want to run 
many jobs parallel except the jobs which are using the same resource.
In CruiseControl.Net you are able to define a queue and the jobs in 
this queue arent allowed to run parallel.


2. Is it possible to run batch commands parallel in a single job?


thank you for reading

Re:Amazon EC2 plugin not waking up stopped slaves

[KEVIN FLEMING (BLOOMBERG/ 731 LEXIN)]

Yes, I use it heavily with my slave templates configured to 'stop' instead of 
'terminate', and the plugin properly restarts the slaves when they are needed.



- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Jan 20 2013 08:57:48

Hi, would log this as a bug but I can't login to jenkins jria (ldap error).

The plugin seems to work fine apart from automatically waking up a slave 
which is stopped.

Logs say it want to provision another node, but it should wake up the 
stopped node and use that.

If I go to the node page and start the slave it comes up fine and the job 
runs.

Jenkins - 1.480.2 LTS
Amazon EC2 plugin 
- 
1.17
Master with no executors, set to no be used
1 slave and can only provision 1 aws node

Anybody use this plugin, with stopped instead of terminate?

Any help would be great.

NPE when sending mails

[Christian Petry]

Hi,
 
have Jenkins 1.499 installed on a Linux machine. Some days ago i have 
upgraded my jenkins installation from 1.465. When a build fails i get the 
following NPE:
 
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 14.774s
[INFO] Finished at: Tue Jan 22 13:02:39 CET 2013
[INFO] Final Memory: 21M/252M
[INFO] 

Projects to build: [MavenProject: ...]
[JENKINS] Archiving ...
[JENKINS] Archiving ...
[JENKINS] Archiving ...
[JENKINS] Archiving ...
Warte bis Jenkins die Datensammlung abgeschlossen hat
ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-users@googlegroups.com
*java.lang.NullPointerException
*at
 
*
hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:246)
*
at 
*hudson.maven.MavenModuleSetBuild$1.(MavenModuleSetBuild.java:215)*
at *
hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:208)
*
at 
*hudson.maven.FilteredChangeLogSet.(FilteredChangeLogSet.java:51)*
at 
*hudson.maven.MavenBuild.getChangeSet(MavenBuild.java:183)*
at 
*hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:452)*
at 
*hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1524)*
at 
*hudson.model.User.getProjects(User.java:444)*
at *
hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:19)
*
at 
*hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101)*
at 
*hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532)*
at 
*hudson.tasks.MailSender.buildCulpritList(MailSender.java:408)*
at 
*hudson.tasks.MailSender.createEmptyMail(MailSender.java:368)*
at 
*hudson.tasks.MailSender.createUnstableMail(MailSender.java:188)*
at 
*hudson.tasks.MailSender.getMail(MailSender.java:159)*
at 
*hudson.tasks.MailSender.execute(MailSender.java:100)*
at 
*hudson.maven.reporters.MavenMailer.end(MavenMailer.java:55)*
at 
*hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103)*
at *
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:758)
*
at *
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592)
*
at 
*hudson.model.Run.execute(Run.java:1543)*
at 
*hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)*
at 
*hudson.model.ResourceController.execute(ResourceController.java:88)*
at 
*huds

Re: Job Queue and parallel batch commands

[Fabian Birk]

I got another question:

There are several teams with Jenkins instances. These instances should be 
able to configure indivdual but all the buildresults have to be visible on 
a "master" jenkins instance.
Ive tried Build Publisher 
(https://wiki.jenkins-ci.org/display/JENKINS/Build+Publisher+Plugin) but 
there is a problem with our proxy. The plugin ignores the proxy settings. 
Even the use of "Reload proxy setup" throws an error "Failes to evaluate".
Is there a possible solution or an alternative?

Thanks for reading =)

Am Dienstag, 22. Januar 2013 14:23:28 UTC+1 schrieb Fabian Birk:
>
> Hello,
>
> I have 2 questions:
>
> 1. Is it possible to set up a queue for similar jobs? I want to run many 
> jobs parallel except the jobs which are using the same resource.
> In CruiseControl.Net you are able to define a queue and the jobs in this 
> queue arent allowed to run parallel.
>
> 2. Is it possible to run batch commands parallel in a single job? 
>
>
> thank you for reading
>

Job Queue and parallel batch commands

[Fabian Birk]

Hello,

I have 2 questions:

1. Is it possible to set up a queue for similar jobs? I want to run many 
jobs parallel except the jobs which are using the same resource.
In CruiseControl.Net you are able to define a queue and the jobs in this 
queue arent allowed to run parallel.

2. Is it possible to run batch commands parallel in a single job? 


thank you for reading

RE: Java error since upgrade to 1.480.2 LTS

[David Aldrich]

Hi Kathi

Thanks for your answer.

David

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Kathi Stutz
> Sent: 22 January 2013 13:09
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Java error since upgrade to 1.480.2 LTS
> 
> 
> Well,
> the problem is indeed caused by the latest version of the JobConfigHistory
> plugin. It happens when you start to build a project which has no
> configuration history yet.
> I'll try to release a hotfix version today. As a workaround right now you can
> just change something in the configuration of the project (like the
> description or disable/enable) and then it should work.
> 
> Kathi Stutz
> 
> 
> 
> 
> 
> On 22.01.2013 13:52, Riccardo Foschia wrote:
> > Just a guess: As the stacktrace suggests the problem seems to be
> > caused by the JobConfigHistory plugin. Try to update this plugin to a
> > newer version.
> >
> > As experience shows after an upgrade of Jenkins it is often necessary
> > to upgrade some plugins.
> >
> > Regards,
> > Riccardo
> >
> > Am 22.01.2013 13:09, schrieb David Aldrich:
> >> Hi
> >>
> >> This morning I upgraded Jenkins from 1.480.1 to 1.480.2 and restarted
> Jenkins.  Now one of my jobs fails with:
> >>
> >>
> >> Started by user 
> >>
> >> FATAL: null
> >>
> >> java.util.NoSuchElementException >> rch?query=java.util.NoSuchElementException>
> >>
> >>  at java.util.AbstractList$Itr.next(Unknown Source)
> >>
> >>  at java.util.Collections.min(Unknown Source)
> >>
> >>  at
> >>
> hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobCon
> >> figBadgeAction.java:79)
> >>
> >>  at
> >>
> hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobCon
> >> figBadgeAction.java:27)
> >>
> >>  at
> >> hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)
> >>
> >>  at hudson.model.Run.execute(Run.java:1497)
> >>
> >>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> >>
> >>  at
> >> hudson.model.ResourceController.execute(ResourceController.java:88)
> >>
> >>  at hudson.model.Executor.run(Executor.java:236)
> >>
> >> How can I fix this please?
> >>
> >> Best regards
> >>
> >> David
> >>
> >>
> 
> 
> 
>  Click
> https://www.mailcontrol.com/sr/FpuJlHZhvx3GX2PQPOmvUkjDae7bB5IgX6L
> Jf70Q!JosxQ7k7W54+eBYlPdIuP1TDa1VfMOl9MwKghm6!2a+jw==  to report
> this email as spam.

Re: Java error since upgrade to 1.480.2 LTS

[Kathi Stutz]

Well,
the problem is indeed caused by the latest version of the
JobConfigHistory plugin. It happens when you start to build a project
which has no configuration history yet.
I'll try to release a hotfix version today. As a workaround right now
you can just change something in the configuration of the project (like
the description or disable/enable) and then it should work.

Kathi Stutz





On 22.01.2013 13:52, Riccardo Foschia wrote:
> Just a guess: As the stacktrace suggests the problem seems to be caused 
> by the JobConfigHistory plugin. Try to update this plugin to a newer 
> version.
>
> As experience shows after an upgrade of Jenkins it is often necessary to 
> upgrade some plugins.
>
> Regards,
> Riccardo
>
> Am 22.01.2013 13:09, schrieb David Aldrich:
>> Hi
>>
>> This morning I upgraded Jenkins from 1.480.1 to 1.480.2 and restarted 
>> Jenkins.  Now one of my jobs fails with:
>>
>>
>> Started by user 
>>
>> FATAL: null
>>
>> java.util.NoSuchElementException
>>
>>  at java.util.AbstractList$Itr.next(Unknown Source)
>>
>>  at java.util.Collections.min(Unknown Source)
>>
>>  at 
>> hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:79)
>>
>>  at 
>> hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:27)
>>
>>  at 
>> hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)
>>
>>  at hudson.model.Run.execute(Run.java:1497)
>>
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
>>
>>  at 
>> hudson.model.ResourceController.execute(ResourceController.java:88)
>>
>>  at hudson.model.Executor.run(Executor.java:236)
>>
>> How can I fix this please?
>>
>> Best regards
>>
>> David
>>
>>

RE: Java error since upgrade to 1.480.2 LTS

[David Aldrich]

Hi Riccardo

Thanks very much for your reply.  I upgraded to the latest version of 
JobConfigHistory when I upgraded Jenkins this morning.

I have now downgraded JobConfigHistory from 2.1 to 2.0 and the error has gone 
away.

Thanks for your help

David

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Riccardo Foschia
> Sent: 22 January 2013 12:53
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Java error since upgrade to 1.480.2 LTS
> 
> Just a guess: As the stacktrace suggests the problem seems to be caused by
> the JobConfigHistory plugin. Try to update this plugin to a newer version.
> 
> As experience shows after an upgrade of Jenkins it is often necessary to
> upgrade some plugins.
> 
> Regards,
> Riccardo
> 
> Am 22.01.2013 13:09, schrieb David Aldrich:
> > Hi
> >
> > This morning I upgraded Jenkins from 1.480.1 to 1.480.2 and restarted
> Jenkins.  Now one of my jobs fails with:
> >
> >
> > Started by user 
> >
> > FATAL: null
> >
> > java.util.NoSuchElementException > ch?query=java.util.NoSuchElementException>
> >
> >  at java.util.AbstractList$Itr.next(Unknown Source)
> >
> >  at java.util.Collections.min(Unknown Source)
> >
> >  at
> >
> hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConf
> > igBadgeAction.java:79)
> >
> >  at
> >
> hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConf
> > igBadgeAction.java:27)
> >
> >  at
> > hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)
> >
> >  at hudson.model.Run.execute(Run.java:1497)
> >
> >  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> >
> >  at
> > hudson.model.ResourceController.execute(ResourceController.java:88)
> >
> >  at hudson.model.Executor.run(Executor.java:236)
> >
> > How can I fix this please?
> >
> > Best regards
> >
> > David
> >
> >
> 
> --
> 
> META-LEVEL Software AG
> Saarbrücker Str. 51
> 66130 Saarbrücken
> Deutschland
> Tel: +49 - 681 / 99687-0
> Fax: +49 - 681 / 99687-99
> Mail: i...@meta-level.de
> Web: www.meta-level.de
> 
> Rechtsform: Aktiengesellschaft
> Sitz: Saarbrücken
> HR B Nr. 13 380 Amtsgericht Saarbrücken
> USt-IdNr. DE 1 38 17
> Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
> Vorsitzender des Aufsichtsrats:  Reinhard Kuhn
> 
> 
> 
>  Click
> https://www.mailcontrol.com/sr/Ju8TsvGZprDGX2PQPOmvUpnwDS3JbRsAf
> M16+IlMWuj2JM92qGxpVw+Bkb+dB2lpDa1VfMOl9MwYNBM7q0TQEQ==  to
> report this email as spam.

Re: Java error since upgrade to 1.480.2 LTS

[Riccardo Foschia]

Just a guess: As the stacktrace suggests the problem seems to be caused 
by the JobConfigHistory plugin. Try to update this plugin to a newer 
version.


As experience shows after an upgrade of Jenkins it is often necessary to 
upgrade some plugins.


Regards,
Riccardo

Am 22.01.2013 13:09, schrieb David Aldrich:

Hi

This morning I upgraded Jenkins from 1.480.1 to 1.480.2 and restarted Jenkins.  
Now one of my jobs fails with:


Started by user 

FATAL: null

java.util.NoSuchElementException

 at java.util.AbstractList$Itr.next(Unknown Source)

 at java.util.Collections.min(Unknown Source)

 at 
hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:79)

 at 
hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:27)

 at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)

 at hudson.model.Run.execute(Run.java:1497)

 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)

 at hudson.model.ResourceController.execute(ResourceController.java:88)

 at hudson.model.Executor.run(Executor.java:236)

How can I fix this please?

Best regards

David




--

META-LEVEL Software AG
Saarbrücker Str. 51
66130 Saarbrücken
Deutschland
Tel: +49 - 681 / 99687-0
Fax: +49 - 681 / 99687-99
Mail: i...@meta-level.de
Web: www.meta-level.de

Rechtsform: Aktiengesellschaft
Sitz: Saarbrücken
HR B Nr. 13 380 Amtsgericht Saarbrücken
USt-IdNr. DE 1 38 17
Vorstände: Dipl.-Inform. Peter Badt und Dipl.-Inform. Peter Raber
Vorsitzender des Aufsichtsrats:  Reinhard Kuhn

Java error since upgrade to 1.480.2 LTS

[David Aldrich]

Hi

This morning I upgraded Jenkins from 1.480.1 to 1.480.2 and restarted Jenkins.  
Now one of my jobs fails with:


Started by user 

FATAL: null

java.util.NoSuchElementException

at java.util.AbstractList$Itr.next(Unknown Source)

at java.util.Collections.min(Unknown Source)

at 
hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:79)

at 
hudson.plugins.jobConfigHistory.JobConfigBadgeAction.onStarted(JobConfigBadgeAction.java:27)

at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)

at hudson.model.Run.execute(Run.java:1497)

at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)

at hudson.model.ResourceController.execute(ResourceController.java:88)

at hudson.model.Executor.run(Executor.java:236)

How can I fix this please?

Best regards

David

Build failure Analyzer Plugin’s odd behaviour

[jhoomsharabi]

Hi 
I am seeing strange problem on my Jenkins 1.496 server running on Solaris box, 
1.  I cannot see Build Failure Analyzer plugin bulb icon under “Build 
History” section instate of icon a text “Identified problems” is visible
2.  When I click on logs under “Build History” for a particular 
failed/unstable build again bulb icon is missing only following messages are 
visible:
 
Identified problems
   
Unit Test Failure
   Contains test case failure
   Indication 1 Indication 2
3.  When I click on “Indication” links, it takes me to build logs but did 
not show the problem with red highlight, I need to click on “Full log” link and 
then navigate to build log to look for highlighted error.
 
Anyone faced this problem in their dev environment with Build Failure Analyzer, 
if yes can anyone help me out and resolving this issue.
 
Thanks,
Jhoom

Re: Jenkins exit code 143 - due to Unexpected termination of the channel

[Richard Mortimer]

On 22/01/2013 10:47, Richard Lavoie wrote:

128+25=153 not 143 the signal is 15 not 25

Damn! Indeed it is. That'll teach me to send messages before first 
coffee of the day.


Well signal 15 is SIGTERM.

My initial thought was that the issue would have been due to the kernel 
OOM (out of memory) killer killing things.


https://wiki.jenkins-ci.org/display/JENKINS/I%27m+getting+OutOfMemoryError

That normally uses SIGKILL (9) but maybe it can use SIGTERM in some 
scenarios.


A quick search showed SIGTERM being used in kernel 2.4 but that doesn't 
seem to be done in the latest linux kernels.


ftp://ftp.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/mm/oom_kill.c

Anyhow the solution will likely lie in finding the cause/source of the 
SIGTERM.


Regards

Richard


Richard

On 2013-01-22, at 04:13, Richard Mortimer  wrote:


Hi,

On 22/01/2013 00:02, BobTheBuilder wrote:

Hello,

I have a long running build that never runs to completion on the slave
computer, it gets "Maven JVM terminated unexpectedly with exit code 143".

Exit codes over 128 signify that the process died due to a signal.

exitcode = 128 + signal number.

That would be signal 25. Assuming that you have a standard linux distribution 
that would be SIGXFSZ.
http://www.lindevdoc.org/wiki/SIGXFSZ

Does your build create large files? If so then maybe your jenkins master or 
slave is running in an environment where an rlimit has been placed on file size.

Regards

Richard


It
does not terminate in the same spot, some times it terminates in 5 minutes
others 30+ minutes (usually 21-22).  If I run the Maven build on my machine,
it runs just fine, completing in 82-92 minutes.

The Jenkins master log says
INFO: PMMT-SystemTest-Milestone3 #814 main build action completed: FAILURE

Jan 17, 2013 1:38:37 PM hudson.remoting.Channel$ReaderThread run
SEVERE: I/O error in channel Channel to Maven [/usr/lib/jvm/java/bin/java,
-Xrs, -Djava.awt.headless=true, -cp,
/opt/ltsapps/jenkins/maven-agent.jar:/opt/ltsapps/jenkins/classworlds.jar,
hudson.maven.agent.Main, /opt/ltsapps/maven,
/opt/ltsapps/jenkins-1.424.2/slave.jar,
/opt/ltsapps/jenkins/maven-interceptor.jar, 46746,
/opt/ltsapps/jenkins/maven2.1-interceptor.jar]
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1037)
Caused by: java.io.EOFException
at
java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1031)

Various Google searches say to check the cpu and memory usage and possibly
add more. However from what I've observed, our machine has 4 CPUs and lots
of free memory that never seems to get used, so I don't think thats it. I've
also tried the -Xms500m -Xmx550m options with no impact.

I've also found sites that referrence problems with Jenkins clients using
SSH ("http://jenkins.361315.n4.nabble.com/fai ... 36397.html") to
communicate with the master but we're using "Lauch slave agents via Java Web
Start". Please note, I will not be able to switch to SSH without an approval
from Congress.  :)

Our Maven goals and options are: clean verify -U -e
-Dtest.machine.qualifier=Z -Dtarget.environment.alias=dev1 -Drest.skip=true
-Dfirefox.skip=true -Dchrome.skip=true -Drunner.timeout.in.seconds=25200
-Drunner.threads.to.use=1 -Ppmmt -DtestFailureIgnore=true
-Dstory.paths.to.include="stories/sf/baf/pmmt/stories/rules/**/*.story"

MAVEN_OPTS is set to: -Xrs -Djava.awt.headless=true

Any help would be appreciated.

Thank you.



--
View this message in context: 
http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347.html
Sent from the Jenkins users mailing list archive at Nabble.com.

Re: Jenkins exit code 143 - due to Unexpected termination of the channel

[Richard Lavoie]

128+25=153 not 143 the signal is 15 not 25

Richard

On 2013-01-22, at 04:13, Richard Mortimer  wrote:

> Hi,
> 
> On 22/01/2013 00:02, BobTheBuilder wrote:
>> Hello,
>> 
>> I have a long running build that never runs to completion on the slave
>> computer, it gets "Maven JVM terminated unexpectedly with exit code 143".
> Exit codes over 128 signify that the process died due to a signal.
> 
> exitcode = 128 + signal number.
> 
> That would be signal 25. Assuming that you have a standard linux distribution 
> that would be SIGXFSZ.
> http://www.lindevdoc.org/wiki/SIGXFSZ
> 
> Does your build create large files? If so then maybe your jenkins master or 
> slave is running in an environment where an rlimit has been placed on file 
> size.
> 
> Regards
> 
> Richard
> 
>> It
>> does not terminate in the same spot, some times it terminates in 5 minutes
>> others 30+ minutes (usually 21-22).  If I run the Maven build on my machine,
>> it runs just fine, completing in 82-92 minutes.
>> 
>> The Jenkins master log says
>> INFO: PMMT-SystemTest-Milestone3 #814 main build action completed: FAILURE
>> 
>> Jan 17, 2013 1:38:37 PM hudson.remoting.Channel$ReaderThread run
>> SEVERE: I/O error in channel Channel to Maven [/usr/lib/jvm/java/bin/java,
>> -Xrs, -Djava.awt.headless=true, -cp,
>> /opt/ltsapps/jenkins/maven-agent.jar:/opt/ltsapps/jenkins/classworlds.jar,
>> hudson.maven.agent.Main, /opt/ltsapps/maven,
>> /opt/ltsapps/jenkins-1.424.2/slave.jar,
>> /opt/ltsapps/jenkins/maven-interceptor.jar, 46746,
>> /opt/ltsapps/jenkins/maven2.1-interceptor.jar]
>> java.io.IOException: Unexpected termination of the channel
>> at hudson.remoting.Channel$ReaderThread.run(Channel.java:1037)
>> Caused by: java.io.EOFException
>> at
>> java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
>> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
>> at hudson.remoting.Channel$ReaderThread.run(Channel.java:1031)
>> 
>> Various Google searches say to check the cpu and memory usage and possibly
>> add more. However from what I've observed, our machine has 4 CPUs and lots
>> of free memory that never seems to get used, so I don't think thats it. I've
>> also tried the -Xms500m -Xmx550m options with no impact.
>> 
>> I've also found sites that referrence problems with Jenkins clients using
>> SSH ("http://jenkins.361315.n4.nabble.com/fai ... 36397.html") to
>> communicate with the master but we're using "Lauch slave agents via Java Web
>> Start". Please note, I will not be able to switch to SSH without an approval
>> from Congress.  :)
>> 
>> Our Maven goals and options are: clean verify -U -e
>> -Dtest.machine.qualifier=Z -Dtarget.environment.alias=dev1 -Drest.skip=true
>> -Dfirefox.skip=true -Dchrome.skip=true -Drunner.timeout.in.seconds=25200
>> -Drunner.threads.to.use=1 -Ppmmt -DtestFailureIgnore=true
>> -Dstory.paths.to.include="stories/sf/baf/pmmt/stories/rules/**/*.story"
>> 
>> MAVEN_OPTS is set to: -Xrs -Djava.awt.headless=true
>> 
>> Any help would be appreciated.
>> 
>> Thank you.
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347.html
>> Sent from the Jenkins users mailing list archive at Nabble.com.
>> 

Re: Jenkins exit code 143 - due to Unexpected termination of the channel

[Richard Mortimer]

Hi,

On 22/01/2013 00:02, BobTheBuilder wrote:

Hello,

I have a long running build that never runs to completion on the slave
computer, it gets "Maven JVM terminated unexpectedly with exit code 143".

Exit codes over 128 signify that the process died due to a signal.

exitcode = 128 + signal number.

That would be signal 25. Assuming that you have a standard linux 
distribution that would be SIGXFSZ.

http://www.lindevdoc.org/wiki/SIGXFSZ

Does your build create large files? If so then maybe your jenkins master 
or slave is running in an environment where an rlimit has been placed on 
file size.


Regards

Richard


It
does not terminate in the same spot, some times it terminates in 5 minutes
others 30+ minutes (usually 21-22).  If I run the Maven build on my machine,
it runs just fine, completing in 82-92 minutes.

The Jenkins master log says
INFO: PMMT-SystemTest-Milestone3 #814 main build action completed: FAILURE

Jan 17, 2013 1:38:37 PM hudson.remoting.Channel$ReaderThread run
SEVERE: I/O error in channel Channel to Maven [/usr/lib/jvm/java/bin/java,
-Xrs, -Djava.awt.headless=true, -cp,
/opt/ltsapps/jenkins/maven-agent.jar:/opt/ltsapps/jenkins/classworlds.jar,
hudson.maven.agent.Main, /opt/ltsapps/maven,
/opt/ltsapps/jenkins-1.424.2/slave.jar,
/opt/ltsapps/jenkins/maven-interceptor.jar, 46746,
/opt/ltsapps/jenkins/maven2.1-interceptor.jar]
java.io.IOException: Unexpected termination of the channel
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1037)
Caused by: java.io.EOFException
at
java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
at hudson.remoting.Channel$ReaderThread.run(Channel.java:1031)

Various Google searches say to check the cpu and memory usage and possibly
add more. However from what I've observed, our machine has 4 CPUs and lots
of free memory that never seems to get used, so I don't think thats it. I've
also tried the -Xms500m -Xmx550m options with no impact.

I've also found sites that referrence problems with Jenkins clients using
SSH ("http://jenkins.361315.n4.nabble.com/fai ... 36397.html") to
communicate with the master but we're using "Lauch slave agents via Java Web
Start". Please note, I will not be able to switch to SSH without an approval
from Congress.  :)

Our Maven goals and options are: clean verify -U -e
-Dtest.machine.qualifier=Z -Dtarget.environment.alias=dev1 -Drest.skip=true
-Dfirefox.skip=true -Dchrome.skip=true -Drunner.timeout.in.seconds=25200
-Drunner.threads.to.use=1 -Ppmmt -DtestFailureIgnore=true
-Dstory.paths.to.include="stories/sf/baf/pmmt/stories/rules/**/*.story"

MAVEN_OPTS is set to: -Xrs -Djava.awt.headless=true

Any help would be appreciated.

Thank you.



--
View this message in context: 
http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347.html
Sent from the Jenkins users mailing list archive at Nabble.com.

Re: Parameterized job with two stages?

[Nalin Makar]

How about creating your own custom parameter? When user enters the ticket
id, you could then use AJAX to look up and display information of the Jira
Ticket on the same page.


On Mon, Jan 21, 2013 at 4:05 AM, syl20bnr  wrote:

> AFAIK, it's not possible to do this out of the box.
>
> You may be able to do this by extending the Free Style Job in the code and
> providing a new Next button or by coding new parameters with dynamic
> content (not sure about this one) but it requires to code a new plugin.
>
> Cheers,
> syl20bnr
>



-- 
-nalin