Re: Jenkins HTTP frontend not acceccable, jenkins/java service needs most CPU/RAM capacity on jenkins service

[jje]

Okay. Thanks for that hint. 

Am Dienstag, 29. September 2015 07:46:43 UTC+2 schrieb Richard Bywater:
>
> Argh - sorry folks. Looks like Inbox decided to requote the entire blob of 
> stuff again :/
>
> Richard.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/30e3e27f-ecc8-489b-bf5f-5f9758497b7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins HTTP frontend not acceccable, jenkins/java service needs most CPU/RAM capacity on jenkins service

[Richard Bywater]

Argh - sorry folks. Looks like Inbox decided to requote the entire blob of
stuff again :/

Richard.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui947iX6-MipLP3PSpzS7e-pOrHU1jTu6HVN777QLgZx2poQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

QA, DEV Urls do not load on Jenkins

[Subramanya Baliga]

Hi Guys,

I have been trying to load my QA and dev urls on jenkins as part of my 
Selenium Webdriver automation scripts.

below is the issues: (These issue are not found when run on my local 
machine)

Note: My jenkins is running on the same local Machine

Mozilla Firefox:
1. When i try to load my QA or Dev URL i do get Authentication Required pop 
up which does not appear in Jenkins but appears when ran through Eclipse.
Verified this by taking screenshot. Screenshot is a white blank page.

Chrome:
1. When i try to load my QA or Dev URL i do get Authentication Required pop 
up, i can enter credentials and after that i am taken to White blank page.

If some 1 could help me go past this issue? or suggest me any work arrounds.

Thanks
Subramanya Baliga

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/40e44411-4d74-4f3f-b841-df7335b1777e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GUI with jenkins not opening on the slave machine

[Rohan Majumdar]

Excellent point  , thanks for the answer...
Open source is even faster and more accurate than proprietary.

Cheers

On Thu, Sep 24, 2015 at 2:03 PM, Victor Martinez <
victormartinezru...@gmail.com> wrote:

> AFAIK, you can as long as you enable the interactive services:
> http://stackoverflow.com/a/19947566 might help
>
> Cheers
>
> On Thursday, 24 September 2015 10:21:23 UTC+2, Rohan Majumdar wrote:
>>
>> So, i guess there is no way to run the service as is and be able to see
>> the automation.
>>
>> Anyways my problem is solved.
>> I am using the JNLP agent manually.
>> Not as a service.
>>
>> Regards and thanks
>> Abbas
>>
>> On Tue, Sep 22, 2015 at 7:00 PM, Victor Martinez 
>> wrote:
>>
>>> That's actually the expected behaviour since Windows services uses
>>> Display 0
>>> -
>>> https://msdn.microsoft.com/en-us/library/windows/desktop/ms683502(v=vs.85).aspx
>>>
>>> Just seen there was already some answers about this feature in the
>>> stackoverflow
>>> -
>>> http://stackoverflow.com/questions/18906753/jenkins-windows-slave-service-does-not-interact-with-desktop
>>>
>>>
>>>
>>> On Tuesday, 22 September 2015 13:57:32 UTC+2, Rohan Majumdar wrote:

 I have observed something weird, that the automation is visible when
 the agent is not running as a windows service.
 The automation visibility worked that way.
 Discovered this by accident.

 On Tuesday, September 22, 2015 at 11:55:05 AM UTC+5:30, Victor Martinez
 wrote:
>
> Let me ask you if you are launching your slave connection via windows
> services (point 6) or via JNLP connections (point 5)
>
>
> 
>
> JNLP shouldn't run in the background AFAIK. Have you tried to run
> those commands manually in the same windows box? Different behaviour?
>
> Cheers
>
>
> On Tuesday, 22 September 2015 07:18:53 UTC+2, Rohan Majumdar wrote:
>>
>> Yeah, I have followed the same tutorial while making the slave.
>> Once again testing works fine but the GUI automation is not visible.
>> I think it happens in the backfround.
>>
>> On Monday, September 21, 2015 at 6:09:37 PM UTC+5:30, Victor Martinez
>> wrote:
>>>
>>> See the below wiki:
>>> -
>>> https://wiki.jenkins-ci.org/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines
>>>
>>> On Monday, 21 September 2015 12:41:04 UTC+2, Rohan Majumdar wrote:

 And yeah I am using windows Vista as a slave.
 Windows 7 is the master

 On Monday, September 21, 2015 at 4:08:16 PM UTC+5:30, Rohan
 Majumdar wrote:
>
> I have installed the java service on the slave, is that not JNLP.
> Can you please elaborate what do you mean by JNLP
>
> On Monday, September 21, 2015 at 12:36:06 PM UTC+5:30, Victor
> Martinez wrote:
>>
>> Hi,
>>
>>  Are you using Windows slaves? If so, have you configured your
>> windows in order to support interactive sessions? IMO, I do prefer 
>> to use
>> JNLP connections rather than Windows service connections since it 
>> does
>> allow interactive sessions by default. Can you try to run your slave 
>> as
>> jnlp connection?
>>
>> Cheers
>>
>>
>> On Monday, 21 September 2015 08:58:20 UTC+2, Rohan Majumdar wrote:
>>>
>>> I have a jenkins slave to run the robotframework test cases. I
>>> am able to get the console prints on the master but no browser ever 
>>> opens
>>> up or anything on the slave.
>>> Ofcourse the test case works pretty fine.
>>> But I am just curious.
>>> How to have the automated test cases play on the slave machine.
>>> There was post which says about running jenkins from the command
>>> line.
>>> But my confusion regarding that is -> Jenkins is configured on
>>> the master then how can we affect
>>> the slave by running jenkins on the console on the master please
>>> elaborate.
>>> There is no jenkins configuration other than the Java service on
>>> the slave machine.
>>>
>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-users/TCf_KhIgHVQ/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/ed126ad3-a644-474a-80d3-be3c51fcda29%40googlegroups.com
>>> 

Re: [workflow-plugin] Aborting doesn't stop downstream jobs

[Anshu Arya]

Actually parallel has nothing to do with it.  If I have a job:

//Parent job

build job: 'test_job'

and another job:

//Downstream job 'test_job'
sleep(3000)

When I Abort the parent job, the downstream job continues.  Is there anyway 
to ensure that downstream jobs are aborted if the parent job is aborted?

On Monday, September 21, 2015 at 10:46:37 PM UTC-7, Anshu Arya wrote:
>
> I have a job that starts more downstream jobs in parallel.  Aborting the 
> job does not abort the downstream jobs.  Is this by design, am I using it 
> wrong, or is this a bug/feature?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/afe922af-185b-472e-99cf-7613e1a8f177%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow-plugin] Sample script for deleting a workflow workspace?

[Oleg Nenashev]

If you specify a boolean parameter, the Workflow code would be...

node {
   if (clean_dir) {
   deleteDir()
   }
   ...
   // Further logic
}

четверг, 10 сентября 2015 г., 21:59:06 UTC+3 пользователь Craig Rodrigues 
написал:
>
> Hi,
>
> James Nord recently fixed:
> "add a cross platform step that will delete all files in the current 
> directory."
>  https://issues.jenkins-ci.org/browse/JENKINS-30346
>
> This does not address:
>
> 'workflow plugin: no opton to "Wipe Out Current Workspace"'
> https://issues.jenkins-ci.org/browse/JENKINS-28382
>
> However, it is a step in the right direction.
>
> Can I use a parameterized build, along with this new change to 
> workflow-plugin to do the following:
>
> (1) I have a workflow.
> (2) With the workflow, I have a build parameter, "do_clean" which by 
> default is set to 0.
> (3) If "do_clean" is set to 1, then logic in the workflow will be 
> triggered which cleans out the files,
> otherwise if "do_clean" is set to 0, then no cleaning occurs.
>
> If this is possible, could someone post a code snippet of a workflow which 
> does this?
>
> Thanks.
> --
> Craig
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/30e8cf50-4d1f-43f8-b9dd-97b531ce0d3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

newbie question - Using a parameterized build, can I use values defined in my build flow DSL

[letstestthis]

Hi

In a sample build, I have this in the flow dsl 

def env = "test"

I have Trigger parameterized build set up and for the predefined 
parameters, I would like to use env, how would I use it for that step. 

I tried env=${env} which did not work. Is there another way I can access 
that value? 

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/064a6fc0-0bc6-4d60-908b-71dfb9f3f0bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disabling the ping thread in Jenkins

[Stephen Connolly]

If you are running 1.580.x then I suspect it is lock contention with
the Queue that is causing the slow page loads.

1.609.x should be much better in that regard... but you may want to
hold back until 1.625.1 as there are some deadlocks that might affect
you in 1.609.1 and 1.609.2 (1.609.3 has most of them fixed, but one
with the old data monitor missed the boat and is in 1.625.1)

On 28 September 2015 at 16:27, Jan Lutenko  wrote:
> Hi,
>
> James, thank you for explanation! I fugured that too...
> Won't make this misinterpretation in the future now.
> Also, that'd be very bad desing and I doubt that community would just let
> this in.
> So the issue is some place else. I wonder if the instance has too many
> Jenkins masters running at once...
> Other do not experience this slowness though
> Anyway, thanks for help, guys!
>
> Cheers,
> Jan
>
> 2015-09-28 12:54 GMT+02:00 James Nord :
>>>
>>> in any other way than the ping thread is terribly slowing down Jenkins by
>>> causing other threads to wait for it:
>>
>>
>>  No the ping thread is sleeping.  The executor thread is waiting on the
>> channel to give it more data.
>>
>> - you got a little confused due to the fact that the ping thread has the
>> name of the channel Object in its threads name (which is the same Object
>> that the executor is wating for...)
>>
>> /James
>>
>> On Thursday, September 24, 2015 at 3:21:33 PM UTC+1, Jan Lutenko wrote:
>>>
>>> Hi,
>>>
>>> I'm not really familiar how this works internally, but looking at thread
>>> dump in Jenkins I can not interpret this
>>> in any other way than the ping thread is terribly slowing down Jenkins by
>>> causing other threads to wait for it:
>>>
>>> Short background: Jenkins 1580.3, running on x64 RHEL with 4 cores and 24
>>> G RAM. Not the only instance on master host, other seem to be feeling
>>> better, I suspect this pinging thread to be the cause of long time page
>>> loading.
>>>
>>> Not listing any further info not to overload someone who's reading this
>>> with useless information.. At the moment.
>>>
>>>
>>> Ping thread for channel hudson.remoting.Channel@32a6cf5b:
>>>
>>> "Ping thread for channel hudson.remoting.Channel@32a6cf5b:" Id=108
>>> Group=main TIMED_WAITING
>>>
>>> at java.lang.Thread.sleep(Native Method)
>>>
>>> at hudson.remoting.PingThread.run(PingThread.java:91)
>>>
>>>
>>> The rest of thread dump (specifically jobs) looks more or less like this:
>>>
>>> Executor #6 for  : executing  # / waiting for
>>> hudson.remoting.Channel@32a6cf5b:
>>>
>>> "Executor #6 for eselivm2v759l : executing mct_up_check #2004 / waiting
>>> for hudson.remoting.Channel@32a6cf5b:" Id=625627 Group=main
>>> TIMED_WAITING
>>>
>>> on hudson.remoting.UserRequest@7654c0aa
>>>
>>> at java.lang.Object.wait(Native Method) - waiting on
>>> hudson.remoting.UserRequest@7654c0aa
>>>
>>> at hudson.remoting.Request.call(Request.java:146)
>>>
>>> at hudson.remoting.Channel.call(Channel.java:751)
>>>
>>> at
>>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173)
>>>
>>> at com.sun.proxy.$Proxy56.join(Unknown Source)
>>>
>>> at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979)
>>>
>>> at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137)
>>>
>>> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97)
>>>
>>> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>>>
>>> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>>>
>>> at
>>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
>>>
>>> at hudson.model.Build$BuildExecution.build(Build.java:199)
>>>
>>> at hudson.model.Build$BuildExecution.doRun(Build.java:160)
>>>
>>> at
>>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
>>>
>>> at hudson.model.Run.execute(Run.java:1745)
>>>
>>> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>>
>>> at hudson.model.ResourceController.execute(ResourceController.java:89)
>>>
>>> at hudson.model.Executor.run(Executor.java:240)
>>>
>>>
>>> Can someone please confirm that my logic here is right/wrong? Also, how
>>> can I disable the ping thread?
>>> I know that adding -Dhudson.remoting.Launcher.pingIntervalSec=-1 to slave
>>> call and a similar
>>> option to master start up can stop the thread from pinging, but will it
>>> be turned off then?
>>>
>>> Any help on this would be very much appreciated as I am stumbling on this
>>> issue not for the first time and hitting a wall as well again.
>>>
>>> Thank you and Best Regards,
>>> Jan
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/eQTbvl1UPCw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.c

Re: Disabling the ping thread in Jenkins

[Jan Lutenko]

Hi,

James, thank you for explanation! I fugured that too...
Won't make this misinterpretation in the future now.
Also, that'd be very bad desing and I doubt that community would just let
this in.
So the issue is some place else. I wonder if the instance has too many
Jenkins masters running at once...
Other do not experience this slowness though
Anyway, thanks for help, guys!

Cheers,
Jan

2015-09-28 12:54 GMT+02:00 James Nord :

> in any other way than the ping thread is terribly slowing down Jenkins by
>> causing other threads to wait for it:
>
>
>  No the ping thread is sleeping.  The executor thread is waiting on the
> channel to give it more data.
>
> - you got a little confused due to the fact that the ping thread has the
> name of the channel Object in its threads name (which is the same Object
> that the executor is wating for...)
>
> /James
>
> On Thursday, September 24, 2015 at 3:21:33 PM UTC+1, Jan Lutenko wrote:
>>
>> Hi,
>>
>> I'm not really familiar how this works internally, but looking at thread
>> dump in Jenkins I can not interpret this
>> in any other way than the ping thread is terribly slowing down Jenkins by
>> causing other threads to wait for it:
>>
>> Short background: Jenkins 1580.3, running on x64 RHEL with 4 cores and 24
>> G RAM. Not the only instance on master host, other seem to be feeling
>> better, I suspect this pinging thread to be the cause of long time page
>> loading.
>>
>> Not listing any further info not to overload someone who's reading this
>> with useless information.. At the moment.
>>
>>
>> Ping thread for channel hudson.remoting.Channel@32a6cf5b:
>>
>> "Ping thread for channel hudson.remoting.Channel@32a6cf5b:" Id=108
>> Group=main TIMED_WAITING
>>
>> at java.lang.Thread.sleep(Native Method)
>>
>> at hudson.remoting.PingThread.run(PingThread.java:91)
>>
>>
>> The rest of thread dump (specifically jobs) looks more or less like this:
>>
>> Executor #6 for  : executing  # / waiting for
>> hudson.remoting.Channel@32a6cf5b:
>>
>> "Executor #6 for eselivm2v759l : executing mct_up_check #2004 / waiting
>> for hudson.remoting.Channel@32a6cf5b:" Id=625627 Group=main
>> TIMED_WAITING
>>
>> on hudson.remoting.UserRequest@7654c0aa
>>
>> at java.lang.Object.wait(Native Method) - waiting on
>> hudson.remoting.UserRequest@7654c0aa
>>
>> at hudson.remoting.Request.call(Request.java:146)
>>
>> at hudson.remoting.Channel.call(Channel.java:751)
>>
>> at
>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173)
>>
>>
>> at com.sun.proxy.$Proxy56.join(Unknown Source)
>>
>> at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979)
>>
>> at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137)
>>
>> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97)
>>
>> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>>
>> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>>
>> at
>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
>>
>>
>> at hudson.model.Build$BuildExecution.build(Build.java:199)
>>
>> at hudson.model.Build$BuildExecution.doRun(Build.java:160)
>>
>> at
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
>>
>>
>> at hudson.model.Run.execute(Run.java:1745)
>>
>> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>
>> at hudson.model.ResourceController.execute(ResourceController.java:89)
>>
>> at hudson.model.Executor.run(Executor.java:240)
>>
>> Can someone please confirm that my logic here is right/wrong? Also, how
>> can I disable the ping thread?
>> I know that adding -Dhudson.remoting.Launcher.pingIntervalSec=-1 to
>> slave call and a similar
>> option to master start up can stop the thread from pinging, but will it
>> be turned off then?
>>
>> Any help on this would be very much appreciated as I am stumbling on this
>> issue not for the first time and hitting a wall as well again.
>>
>> Thank you and Best Regards,
>> Jan
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/eQTbvl1UPCw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/25dfbc23-8313-48a3-8616-a9b4033917f3%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Z poważaniem,
Jan Lutenko

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view thi

Re: Understanding Jenkins builds and processes when running in parallel

[Maciej Jaros]

John Wadleigh (2015-09-28 09:58):

Hello all,

I am trying to find some documentation on how Jenkins handles multiple 
builds on a specific node. Does it spawn separate processes? threads? 
How does it manage parallel builds?  And can I see these running on 
the OS? I have checked on our Linux OS but cannot find specific 
processes that seem to match the build.   We have a Linux machine with 
16 CPUs, and I would like to make sure that Jenkins is using these 
CPUs when running 10 build jobs at the same time.  How can I monitor 
this better and understand it better?


AFAIK build operations are handled by JVM so you would see threads for 
builds there. Not sure if every build is a single thread and if they are 
reused in any way.


Of course build might run another operation (especially if running shell 
commands), which might be visible in the OS itself.


Regards,
Nux.

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/56092DC7.3000403%40mol.com.pl.
For more options, visit https://groups.google.com/d/optout.

Maby be the "JenkinsLinuxStartupScript" is wrong?

[Wei Chen]

I found this script by 
"https://wiki.jenkins-ci.org/display/JENKINS/JenkinsLinuxStartupScript?showComments=true&showCommentArea=true#addcomment";.

At the very beginning it wrote:
...
This assumes that Jenkins is installed in /home/jenkins, Tomcat is 
installed in /home/jenkins/apache-tomcat-6.0.18, and ...


But I would like to say this is a script for starting/stopping Tomcat, not 
for the Jenkins. One has to deploy the Jenkins to Tomcats webapps. Right?


Regards

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6dd584ce-1c1d-4f1c-b333-e79e4d734373%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to update environment variable value via EnvInject plugin

[Quang Truong]

Hi,

I'm using EnvInject plugin to pass the variables across jobs but in one job 
the value of one variable might change within that job and I want to update 
that variable's value within that job.

I have tried to add:
echo var1=%new value%>>"%workspace%\glob.prop"
then use EnvInject this glob.prop into the Environment variable.

However, within the job, the value is still the old one, but after the job 
finishes, the new value is updated within the environment variables list of 
that build. Not sure how to update the value right away so I can use that 
value.

PS: when I write out the glob.prop it has 2 line of the same variable
var1=old value
var1=new value

Thanks,
Quang

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1f553b0d-dae0-454f-89d9-729ff4a8a691%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Batch command with slave mode configuration

[Quang Truong]

I have found the root cause: because I changed the way to invoke the slave 
and the account running the slave connection doesn't have enough permission 
so that Jenkins doesn't have permission to see nbtstat command.

A workaround is running the slave.jar to call the jnlp from Jenkins master 
by the java which is defined in Javahome.

Regards,
Quang

On Friday, September 18, 2015 at 1:15:39 AM UTC+7, Quang Truong wrote:

> Thanks Victor!
>
> I have tried with backlash (actually we can use even Linux syntax here) 
> and use %windir% instead of C:\Windows but still got the syntax error. I 
> don't know how to correct the syntax for this block in FOR command
>
> '"%windir%\System32\nbtstat.exe" -A %VM_IP% ^|FIND "<20>"'
>
> Thanks,
> Quang
>
> On Thursday, September 17, 2015 at 2:39:33 AM UTC+7, Quang Truong wrote:
>
>> Dear all,
>>
>> I have encountered an issue like this:
>>
>> - If I setup a slave by downloading and running the jnlp file (no need to 
>> install as Window service, just leave the java dialog as connected 
>> process). Then I can run this batch command:
>>
>> setlocal EnableDelayedExpansion
>> FOR /f "tokens=1 delims=<" %%G IN ('nbtstat -A %VM_IP% ^|FIND "<20>"') DO 
>> (
>> SET Test_Machine_Name=%%G
>> echo Test_Machine_Name=!Test_Machine_Name!
>> )
>>
>> to return a target machine name (from provide IP %VM_IP%)
>>
>> - But if I run the commandline to setup the slave ( java -jar slave.jar 
>> -jnlpUrl http://:8080/computer//slave-agent.jnlp 
>> -secret ) then I encounter this error: 
>> 'nbtstat' is not recognized as an internal or external command,
>> operable program or batch file.
>> I have tried to point the absolute path of the nbtstat
>>
>> setlocal EnableDelayedExpansion
>> FOR /f "tokens=1 delims=<" %%G IN ('"C:/Windows/System32/nbtstat.exe -A 
>> %VM_IP%" ^|FIND "<20>"') DO (
>> SET Test_Machine_Name=%%G
>> echo Test_Machine_Name=!Test_Machine_Name!
>> )
>> then got the syntax incorrect.
>>
>> Please help to guide for solving this issue
>>
>> Thanks,
>> Quang
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/33e3f88b-d13d-46dc-85d9-c756d8b15d8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Displaying image in console output

[Brian]

I'm running some shell commands and the last one is to download an image 
from a fixed url

+ wget http://10.10.10.10/screenshot.jpg 
--2015-09-28 12:21:29--  http://10.10.10.60/screenshot.jpg 

Connecting to 10.55.0.60:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 36318 (35K) [image/jpeg]
Saving to: `screenshot.jpg.1'

 0K .. .. .. .100%  314M=0s


Is there a way to display this image in the console output?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f630d41c-8ccf-4267-8892-d2003ac7017d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Disabling the ping thread in Jenkins

[James Nord]

>
> in any other way than the ping thread is terribly slowing down Jenkins by 
> causing other threads to wait for it:


 No the ping thread is sleeping.  The executor thread is waiting on the 
channel to give it more data.

- you got a little confused due to the fact that the ping thread has the 
name of the channel Object in its threads name (which is the same Object 
that the executor is wating for...)

/James

On Thursday, September 24, 2015 at 3:21:33 PM UTC+1, Jan Lutenko wrote:
>
> Hi,
>
> I'm not really familiar how this works internally, but looking at thread 
> dump in Jenkins I can not interpret this
> in any other way than the ping thread is terribly slowing down Jenkins by 
> causing other threads to wait for it:
>
> Short background: Jenkins 1580.3, running on x64 RHEL with 4 cores and 24 
> G RAM. Not the only instance on master host, other seem to be feeling 
> better, I suspect this pinging thread to be the cause of long time page 
> loading.
>
> Not listing any further info not to overload someone who's reading this 
> with useless information.. At the moment.
>
>
> Ping thread for channel hudson.remoting.Channel@32a6cf5b: 
>
> "Ping thread for channel hudson.remoting.Channel@32a6cf5b:" Id=108 
> Group=main TIMED_WAITING
>
> at java.lang.Thread.sleep(Native Method)
>
> at hudson.remoting.PingThread.run(PingThread.java:91)
>
>
> The rest of thread dump (specifically jobs) looks more or less like this:
>
> Executor #6 for  : executing  # / waiting for 
> hudson.remoting.Channel@32a6cf5b: 
>
> "Executor #6 for eselivm2v759l : executing mct_up_check #2004 / waiting 
> for hudson.remoting.Channel@32a6cf5b:" Id=625627 Group=main 
> TIMED_WAITING 
>
> on hudson.remoting.UserRequest@7654c0aa 
>
> at java.lang.Object.wait(Native Method) - waiting on 
> hudson.remoting.UserRequest@7654c0aa 
>
> at hudson.remoting.Request.call(Request.java:146) 
>
> at hudson.remoting.Channel.call(Channel.java:751) 
>
> at 
> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173)
>  
>
>
> at com.sun.proxy.$Proxy56.join(Unknown Source)
>
> at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979)
>
> at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) 
>
> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) 
>
> at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) 
>
> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 
>
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
>  
>
>
> at hudson.model.Build$BuildExecution.build(Build.java:199) 
>
> at hudson.model.Build$BuildExecution.doRun(Build.java:160) 
>
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) 
>
>
> at hudson.model.Run.execute(Run.java:1745) 
>
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
>
> at hudson.model.ResourceController.execute(ResourceController.java:89) 
>
> at hudson.model.Executor.run(Executor.java:240)
>
> Can someone please confirm that my logic here is right/wrong? Also, how 
> can I disable the ping thread? 
> I know that adding -Dhudson.remoting.Launcher.pingIntervalSec=-1 to slave 
> call and a similar
> option to master start up can stop the thread from pinging, but will it be 
> turned off then?
>
> Any help on this would be very much appreciated as I am stumbling on this 
> issue not for the first time and hitting a wall as well again.
>
> Thank you and Best Regards,
> Jan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/25dfbc23-8313-48a3-8616-a9b4033917f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Preventing two jobs to run simultaneously on same node but allowing to run simultaneously on different nodes

[Victor Martinez]

Hi there,

 I believe "Throttle concurrent builds" plugin should work, in fact, it's 
exactly what I don in roder to run different builds. Have you tried with 
the below setup?


  
  I'm based on:
- Jenkins ver. 1.599
- throttle-concurrents ver. 1.8.3

I hope it helps

Cheers

On Monday, 28 September 2015 09:35:14 UTC+2, ozonec...@gmail.com wrote:
>
> Hi Jenkins Users,
>
> I am using *Jenkins 1.609*
>
> I have a requirement wherein 
>
> *1) no two jobs can execute simultaneously on the same node but 2) they 
> can execute simultaneously when triggered on different nodes.*
> No of executors configured on all slave nodes is 1. 
>
> Default Jenkins behavior:
> If job A and job B, both are triggered on same node then Job B goes in 
> executor starvation state because build is waiting for "too long" compared 
> to the time it takes to execute it. Once job B goes in this state, it gets 
> stuck and is not picked up for building.
>
> Have tried using "Exclusion plugin". It helps in achieving first point but 
> not the second one.
> Also, have tried using Throttle concurrent builds plugin but still Job B 
> goes into executor starvation state.
>
> Is there any way wherein I can achieve both the points i.e. prevent 
> running the jobs simultaneously on same node but can run on different nodes 
> and without the second job going into executor starvation state as I cannot 
> change the sequence of the jobs??
>
> Thanks in advance!
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d1684b31-8673-48c8-9a86-233b9ed8b3e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins SCP Plugin

[Akash Gangil]

Hi, 

I am using Jenkins SCP plugin v1.8. However, I am unable to see the options:
(1) Copy Console Log
(2) Copy after failure. 

I can only see the option for Keep Hierarchy.

​

Could someone please tell me how to enable those two options?

Jenkins version 1.630.

thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8d575f58-8a30-410a-8865-3888c445053a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

o control deployment and tests on iSeries-hosts

[Wilmer_T]

Hi there!
How should I go about to run deployment and tests on iSeries (former 
AS/400) with Jenkins...?

Any references or caveats to identify and mitigate?

Med vänlig hälsning,

   /Wilmer_T

...här skiner solen...

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7a680d9c-2956-44b3-9bd7-c4cd1b1f0f93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Understanding Jenkins builds and processes when running in parallel

[John Wadleigh]

Hello all,

I am trying to find some documentation on how Jenkins handles multiple 
builds on a specific node. Does it spawn separate processes? threads? How 
does it manage parallel builds?  And can I see these running on the OS? I 
have checked on our Linux OS but cannot find specific processes that seem 
to match the build.   We have a Linux machine with 16 CPUs, and I would 
like to make sure that Jenkins is using these CPUs when running 10 build 
jobs at the same time.  How can I monitor this better and understand it 
better?

Your help is appreciated,
Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/332495fe-5ce7-4b1d-92d4-211d38fc4c04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Preventing two jobs to run simultaneously on same node but allowing to run simultaneously on different nodes

[ozonecatalyst]

Hi Jenkins Users,

I am using *Jenkins 1.609*

I have a requirement wherein 

*1) no two jobs can execute simultaneously on the same node but 2) they can 
execute simultaneously when triggered on different nodes.*
No of executors configured on all slave nodes is 1. 

Default Jenkins behavior:
If job A and job B, both are triggered on same node then Job B goes in 
executor starvation state because build is waiting for "too long" compared 
to the time it takes to execute it. Once job B goes in this state, it gets 
stuck and is not picked up for building.

Have tried using "Exclusion plugin". It helps in achieving first point but 
not the second one.
Also, have tried using Throttle concurrent builds plugin but still Job B 
goes into executor starvation state.

Is there any way wherein I can achieve both the points i.e. prevent running 
the jobs simultaneously on same node but can run on different nodes and 
without the second job going into executor starvation state as I cannot 
change the sequence of the jobs??

Thanks in advance!


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6047ebf5-66b6-4595-a8a1-590c6470515d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.