Re: Build Flow Question

[Benjamin Lau]

Use guard/rescue.

guard {
  parallel (
  { build("jobA", ...) },
  { build("jobB", ...) },
  ...
  )
} rescue {
  build("jobC", ...)
}

That's how I've dealt with it.  See "Guard / Rescue" on the Build Flow
Plugin page in the Jenkins wiki:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin


Ben

On Wed, Jul 3, 2013 at 7:06 PM, Slide  wrote:
> I am using the build flow plugin, which I have to say is incredible, so
> thanks! I had a question about how I can have something ALWAYS run after a
> set of parallel builds. I have something like the following:
>
> parallel (
> { build("jobA", ...) },
> { build("jobB", ...) },
> ...
> )
>
> build("jobC", ...)
>
> I want to make sure that jobC is ALWAYS built regardless of the outcome of
> the other jobs, but it seems like if one of the jobs inside the parallel
> fails, then the jobs outside don't run. Do I just need to wrap the whole
> parallel in an ignore {} ?
>
> Thanks!
>
> slide
>
> --
> Website: http://earl-of-code.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

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

Build Flow Question

[Slide]

I am using the build flow plugin, which I have to say is incredible, so
thanks! I had a question about how I can have something ALWAYS run after a
set of parallel builds. I have something like the following:

parallel (
{ build("jobA", ...) },
{ build("jobB", ...) },
...
)

build("jobC", ...)

I want to make sure that jobC is ALWAYS built regardless of the outcome of
the other jobs, but it seems like if one of the jobs inside the parallel
fails, then the jobs outside don't run. Do I just need to wrap the whole
parallel in an ignore {} ?

Thanks!

slide

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

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

Re: Half of the project configure screen is grayed out with Loading message!

[Sameh Tawfik]

Hi Vincent,
 
Thanks for the info. Any rough idea when is the next release 1.522 will be 
available? We can not downgrade, because as mentioned below the previous 
version of Jenkins would not work with another plugin "FindBugs".
 
  Sameh

On Wednesday, July 3, 2013 11:52:37 AM UTC-7, Vincent Latombe wrote:

> Hi, 
>
> it's JENKINS-18585, and it will be fixed in 1.522. You should 
> downgrade the core for the time being. 
>
> Cheers, 
>
> Vincent 
> Vincent 
>
>
> 2013/7/3 Sameh Tawfik >: 
> > Hi Lary, 
> > 
> > Thanks for your quick response. 
> > 
> > After checking all the installed plugins, it turned out "Environment 
> > Injector" Plugin (EnvInject Plugin) version 1.87, is the one causing 
> this 
> > problem! 
> > 
> > We need to use this plugin for all our builds, since we need to pass 
> > environment variables to each build. 
> > 
> > This plugin was working fine with the previous version of Jenkins 
> version 
> > 1.519? 
> > 
> > I do not see an option to install a previous version of "EnvInject" 
> plugin 
> > to see if the previous would work with the latest version of Jenkins. 
> > 
> > We need to use the newer version of Jenkins version 1.521, because the 
> > previous version would not work with "FindBugs" plugin. 
> > 
> > I hope this problem will be fixed in the next release of Jenkins? 
> > 
> > On Wednesday, July 3, 2013 9:33:05 AM UTC-7, Larry Shatzer, Jr. wrote: 
> >> 
> >> Check the logs when this is happening. I've had issues with some old 
> >> plugins in the past with similar behavior. Luckily they were plugins 
> that 
> >> were no longer used in my instance, so removal of them fixed it for me. 
> I'd 
> >> also check your javascript console for any possible errors like 
> >> https://issues.jenkins-ci.org/browse/JENKINS-18585 (which mentioned 
> some 
> >> plugins). 
> >> 
> >> 
> >> On Wed, Jul 3, 2013 at 10:26 AM, Sameh Tawfik  
> wrote: 
> >>> 
> >>> 
> >>> 
> >>> Hi, 
> >>> 
> >>> We just installed Jenkins ver. 1.521, and now whenever we open any 
> >>> project to update some configuration by clicking on the project 
> configure 
> >>> tab, we see the first half of the configuration screen is grayed out 
> up to 
> >>> "Load script and properties files from the master" field with 
> "Loading" 
> >>> message displayed on this grayed out area, and the other half of the 
> project 
> >>> is fine, meaning it is not grayed out and we can update any field in 
> this 
> >>> area? 
> >>> 
> >>> I  restarted Jenkins, but that did not make any difference! The 
> problem 
> >>> is still there! 
> >>> 
> >>> This seems to be a bug in Jenkins, because why half of the screen is 
> >>> grayed out, and the other have is not? 
> >>> 
> >>> Is this a new problem? Does anyone knows if there is a fix to this 
> >>> problem? 
> >>> 
> >>> Sameh 
> >>> 
> >>> -- 
> >>> You received this message because you are subscribed to the Google 
> Groups 
> >>> "Jenkins Users" group. 
> >>> To unsubscribe from this group and stop receiving emails from it, send 
> an 
> >>> email to jenkinsci-use...@googlegroups.com. 
> >>> 
> >>> For more options, visit https://groups.google.com/groups/opt_out. 
> >>> 
> >>> 
> >> 
> >> 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Jenkins Users" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to jenkinsci-use...@googlegroups.com . 
> > For more options, visit https://groups.google.com/groups/opt_out. 
> > 
> > 
>

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

Re: How to keep Unix process alive after job is completed?

[Richard Bywater]

Could you just have the server process setup as a service and then "start"
the service?

Richard.

On Fri, Apr 26, 2013 at 8:08 PM, hezjing  wrote:

> Hi
>
> I have a job which will be run in an Linux slave.
>
> This job will execute a shell command to start a server process which will
> run forever. Unfortunately this process is terminated when the job is
> finished.
>
> When I tested this using PuTTY, the server process is still alive after I
> logged-in and out several times.
>
> May I know how to keep a Unix process alive after the job is completed?
>
>
> --
>
> Hez
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Build fails with "UNSTABLE" - but Maven run successfully

[Johannes Schneider]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi guys,

this[1] are the last lines of  the console output.
The build is marked as unstable (yellow). I have no idea what might
have gone wrong.

This job used to run just fine. So I don't know what might have changed.
I did an upgraded of jenkins and updated the plugins. So maybe it
might be related to that?

What could I do to get an idea why the build failed?



Thanks,

Johannes




[1] Last lines of the console output:

[INFO]
- 
[INFO] BUILD SUCCESS
[INFO]
- 
[INFO] Total time: 11:52.012s
[INFO] Finished at: Wed Jul 03 22:42:51 CEST 2013
[INFO] Final Memory: 48M/224M
[INFO]
- 
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
Waiting for Jenkins to finish collecting data
channel stopped
Terminating xvnc.
$ /usr/bin/vncserver -kill :66
Killing Xvnc4 process ID 5382
Build did not succeed and the project is configured to only push after
a successful build, so no pushing will occur.
Finished: UNSTABLE
- -- 

Johannes Schneider - blog.cedarsoft.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJR1JD2AAoJEAytD9R7Qv6dQecH/03TCn29mZd8tDQL4qpjH27q
Umlpf05GBRZ//qSXndlfPGHr4nQ3PVO2YTWzcGN1IkLg2br8HqIwSQ95k8bDxPTh
qAsyM46gSWAVnBLytLoOhCJYGyGGFXrKOUeMBiCWMN6SeARD2t5HX73y6t6UTDdG
GoNBl6T80wEBsg51YhqLUnIhdZiJogbtSl9Tse/M9s/Z580dMvxxXQfKM8cjZn5z
KNE52xDnojqDN9L3l9PQrsTzvy/imwA1GpffzAtwPb5AzUK4FBLfrFtPLwV/OW0O
sktotbxJuD+dAV4QrLB/8p+h8Kvqth+kIQivYFGsgtiJIcP77ftXKWIrPT19Fkc=
=mEo8
-END PGP SIGNATURE-

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

Re: HTML Publisher plugin no longer listed

[Larry Shatzer, Jr.]

There's a problem with the wiki and that page I see lots of exceptions
trying to load up
https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Artifactuploaders,
which is where that plugin should be shown. If you add a random query
parameter to the URL, like
https://wiki.jenkins-ci.org/display/JENKINS/Plugins?a=a,
then it will show up, so it might be something wrong with the caching that
the wiki has.


On Wed, Jul 3, 2013 at 12:52 PM, bl0ck3r  wrote:

> The HTML Publisher plugin is no longer listed on the following page... can
> some one bring it back please?
>
> https://wiki.jenkins-ci.org/display/JENKINS/Plugins
>
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Re: Half of the project configure screen is grayed out with Loading message!

[Vincent Latombe]

Hi,

it's JENKINS-18585, and it will be fixed in 1.522. You should
downgrade the core for the time being.

Cheers,

Vincent
Vincent


2013/7/3 Sameh Tawfik :
> Hi Lary,
>
> Thanks for your quick response.
>
> After checking all the installed plugins, it turned out "Environment
> Injector" Plugin (EnvInject Plugin) version 1.87, is the one causing this
> problem!
>
> We need to use this plugin for all our builds, since we need to pass
> environment variables to each build.
>
> This plugin was working fine with the previous version of Jenkins version
> 1.519?
>
> I do not see an option to install a previous version of "EnvInject" plugin
> to see if the previous would work with the latest version of Jenkins.
>
> We need to use the newer version of Jenkins version 1.521, because the
> previous version would not work with "FindBugs" plugin.
>
> I hope this problem will be fixed in the next release of Jenkins?
>
> On Wednesday, July 3, 2013 9:33:05 AM UTC-7, Larry Shatzer, Jr. wrote:
>>
>> Check the logs when this is happening. I've had issues with some old
>> plugins in the past with similar behavior. Luckily they were plugins that
>> were no longer used in my instance, so removal of them fixed it for me. I'd
>> also check your javascript console for any possible errors like
>> https://issues.jenkins-ci.org/browse/JENKINS-18585 (which mentioned some
>> plugins).
>>
>>
>> On Wed, Jul 3, 2013 at 10:26 AM, Sameh Tawfik  wrote:
>>>
>>>
>>>
>>> Hi,
>>>
>>> We just installed Jenkins ver. 1.521, and now whenever we open any
>>> project to update some configuration by clicking on the project configure
>>> tab, we see the first half of the configuration screen is grayed out up to
>>> "Load script and properties files from the master" field with "Loading"
>>> message displayed on this grayed out area, and the other half of the project
>>> is fine, meaning it is not grayed out and we can update any field in this
>>> area?
>>>
>>> I  restarted Jenkins, but that did not make any difference! The problem
>>> is still there!
>>>
>>> This seems to be a bug in Jenkins, because why half of the screen is
>>> grayed out, and the other have is not?
>>>
>>> Is this a new problem? Does anyone knows if there is a fix to this
>>> problem?
>>>
>>> Sameh
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jenkinsci-use...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

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

HTML Publisher plugin no longer listed

[bl0ck3r]

The HTML Publisher plugin is no longer listed on the following page... can 
some one bring it back please?

https://wiki.jenkins-ci.org/display/JENKINS/Plugins

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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Jenkins execute part of the job on master?

[lom109]

You can produce this behaviour if you decide to use the Groovy Plugin.

It lets you "set up the environment" using groovy ON the master... which
means you can run arbitrary setup logic on the master before you "copy
over" any artifacts to the slave.

Which isn't what the OP requested.. but throwing that out there.

On Tue, Jul 2, 2013 at 1:07 PM, Mark Waite  wrote:

> As far as I can tell, a job executes on a single node, whether master or
> slave.  I'm not aware of any facility that allows a Jenkins job to move
> execution steps to a node different than the node executing the job.
>
> Mark Waite
>
>   --
>  *From:* Michael Lasevich 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Tuesday, July 2, 2013 10:17 AM
> *Subject:* Jenkins execute part of the job on master?
>
> Trying to understand master-slave relationship in jenkins node.
>
> Is it possible to execute MOST of the job (build) on a slave node, but the
> final step (one or more publishers?) on the master node?
>
> If I am writing my own plug in, how do I control where the plugin
> executes? Or can I?
>
>
> Thanks,
>
> -M
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
>
>--
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Re: Half of the project configure screen is grayed out with Loading message!

[Sameh Tawfik]

Hi Lary,
 
Thanks for your quick response.
 
After checking all the installed plugins, it turned out "Environment 
Injector" Plugin (EnvInject Plugin) version 1.87, is the one causing this 
problem!  
 
We need to use this plugin for all our builds, since we need to pass 
environment variables to each build. 
 
This plugin was working fine with the previous version of Jenkins version 
1.519?  
 
I do not see an option to install a previous version of "EnvInject" plugin 
to see if the previous would work with the latest version of Jenkins. 
 
We need to use the newer version of Jenkins version 1.521, because the 
previous version would not work with "FindBugs" plugin.
 
I hope this problem will be fixed in the next release of Jenkins?

On Wednesday, July 3, 2013 9:33:05 AM UTC-7, Larry Shatzer, Jr. wrote:

> Check the logs when this is happening. I've had issues with some old 
> plugins in the past with similar behavior. Luckily they were plugins that 
> were no longer used in my instance, so removal of them fixed it for me. I'd 
> also check your javascript console for any possible errors like 
> https://issues.jenkins-ci.org/browse/JENKINS-18585 (which mentioned some 
> plugins).
>
>
> On Wed, Jul 3, 2013 at 10:26 AM, Sameh Tawfik 
> > wrote:
>
>>  
>>  
>> Hi,  
>>  
>> We just installed Jenkins ver. 1.521, and now whenever we open any 
>> project to update some configuration by clicking on the project configure 
>> tab, we see the first half of the configuration screen is grayed out up to 
>> "Load script and properties files from the master" field with "Loading" 
>> message displayed on this grayed out area, and the other half of the 
>> project is fine, meaning it is not grayed out and we can update any field 
>> in this area?
>>  
>> I  restarted Jenkins, but that did not make any difference! The problem 
>> is still there!
>>  
>> This seems to be a bug in Jenkins, because why half of the screen is 
>> grayed out, and the other have is not?
>>  
>> Is this a new problem? Does anyone knows if there is a fix to this 
>> problem?
>>  
>> Sameh
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

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

Re: Half of the project configure screen is grayed out with Loading message!

[Larry Shatzer, Jr.]

Check the logs when this is happening. I've had issues with some old
plugins in the past with similar behavior. Luckily they were plugins that
were no longer used in my instance, so removal of them fixed it for me. I'd
also check your javascript console for any possible errors like
https://issues.jenkins-ci.org/browse/JENKINS-18585 (which mentioned some
plugins).


On Wed, Jul 3, 2013 at 10:26 AM, Sameh Tawfik  wrote:

>
>
> Hi,
>
> We just installed Jenkins ver. 1.521, and now whenever we open any project
> to update some configuration by clicking on the project configure tab, we
> see the first half of the configuration screen is grayed out up to "Load
> script and properties files from the master" field with "Loading" message
> displayed on this grayed out area, and the other half of the project is
> fine, meaning it is not grayed out and we can update any field in this area?
>
> I  restarted Jenkins, but that did not make any difference! The problem is
> still there!
>
> This seems to be a bug in Jenkins, because why half of the screen is
> grayed out, and the other have is not?
>
> Is this a new problem? Does anyone knows if there is a fix to this problem?
>
> Sameh
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Half of the project configure screen is grayed out with Loading message!

[Sameh Tawfik]

 
 
Hi,  
 
We just installed Jenkins ver. 1.521, and now whenever we open any project 
to update some configuration by clicking on the project configure tab, we 
see the first half of the configuration screen is grayed out up to "Load 
script and properties files from the master" field with "Loading" message 
displayed on this grayed out area, and the other half of the project is 
fine, meaning it is not grayed out and we can update any field in this area?
 
I  restarted Jenkins, but that did not make any difference! The problem is 
still there!
 
This seems to be a bug in Jenkins, because why half of the screen is grayed 
out, and the other have is not?
 
Is this a new problem? Does anyone knows if there is a fix to this problem?
 
Sameh

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

Re: How to get all builds of a project via API

[Tim Ford]

curl -d 'script=println Jenkins.instance.getItem(jobName).builds.each{ 
println "${it.number}:${it.startTimeInMillis}:${it.duration}:${it.result}" 
};' http://localhost:8080/scriptText

On Wednesday, July 3, 2013 6:55:17 AM UTC-5, Dirk Heinrichs wrote:
>
>  Hi,
>
>  
>
> I’ve got a small Groovy script to get some data for all builds of a given 
> project:
>
>  
>
> *import* hudson.model.*
>
>  
>
> *def* jobName = args[0]
>
>  
>
> *def* job = Hudson.instance.getItem(jobName)
>
> *def* builds = job.getBuilds()
>
> builds.each
>
> {
>
>println (it.getNumber()+":"+it.getStartTimeInMillis()+":"+it
> .getDuration()+":"+it.getResult().toString())
>
> }
>
>  
>
> This one works as expected. However, I only call this script from within a 
> Perl script because I can’t get all the data using either XML or JSON api, 
> which only gives me the data for the last N builds instead of all builds, 
> using an URL like ‘http://server/job/MyJob/api/xml?tree=builds[number,url]’. 
> How do I get the data for ALL builds using either JSON or XML?
>
>  
>
> Possible workaround: use ‘?tree=firstBuild[number],lastBuild[number]’ and 
> construct the URL for each build myself.
>
>  
>
> Thanks...
>
>  
>
>Dirk
>
>  
>
> [image: cid:image003.gif@01CB3EF6.319079E0]
>
> *Dirk Heinrichs*, Senior Systems Engineer, Infrastructure
>
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
>
> *Tel:* +49 2226 159 1149
>
> *Email:* dirk.heinri...@recommind.com 
>
> *Skype:* dirk.heinrichs.recommind
>
> *www.recommind.com* 
>
>  
>  

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

Folders plugin throwing exception in Guice injection

[Jerry]

Hi, I was trying to track down a memory leak in Jenkins (or a plugin) and I 
came across the following in my log file. I don't think it has anything to 
do with the memory leak, and I haven't noticed any effects of it, just 
thought someone (e.g. Stephen Connelly) might like to know.

-

Jul 02, 2013 3:55:10 PM hudson.ExtensionFinder$GuiceFinder$4$1 get
WARNING: Failed to instantiate. Skipping this component
com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, java.lang.NoClassDefFoundError: 
nectar/plugins/rbac/groups/ProxyGroupContainer
  at 
com.cloudbees.hudson.plugins.folder.properties.FolderProxyGroupContainer$DescriptorImpl.(FolderProxyGroupContainer.java:178)

1 error
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at com.google.inject.Scopes$1$1.get(Scopes.java:59)
at hudson.ExtensionFinder$GuiceFinder$4$1.get(ExtensionFinder.java:422)
at 
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at 
com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391)
at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382)
at hudson.ExtensionFinder._find(ExtensionFinder.java:151)
at 
hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:318)
at hudson.ExtensionList.load(ExtensionList.java:295)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
at hudson.ExtensionList.getComponents(ExtensionList.java:149)
at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
at hudson.ExtensionList.iterator(ExtensionList.java:138)
at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:101)
at 
org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)
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.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
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 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
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 
org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at 
org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
at 
org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
at 
org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
at 
org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFil

Re: How to keep Unix process alive after job is completed?

[Tim Ford]

John, your issue might be unrelated to Jenkins.

See:  
http://stackoverflow.com/questions/285015/linux-prevent-a-background-process-from-being-stopped-after-closing-ssh-client


On Wednesday, July 3, 2013 5:42:10 AM UTC-5, John Vacz wrote:
>
>  We have a job executing a shell script (on a slave) to restart one dev 
> appserver on a remote server if it does not work properly (dont bother why 
> its not working):
>
>   # BUILD_ID=dontKillMe
>   ssh us...@some.remote.server  exec 
> /path/to/appserver/force_restart_script arg1
>
> The "force_restart_script" on the *remote* server doing the following:
>
>   # find and kill the old appserver process
>   kill_appserver_script arg1
>   # start appserver with specified argument
>   /path/to/appserver/start_appserver_script arg1
>
> At the end, the old appserver process was killed, and the new appserver 
> process was also terminated. How can i keep this from happening? The 
> BUILD_ID=dontKillMe in job configureation doesn't seem to work (that would 
> only keep the ssh from being terminated on the slave, right?), or I should 
> actually set the BUILD_ID in the remote ssh shell?
>
> Any help is very much appreciated!
>
> -jv
>
> Am 26.04.2013 10:16, schrieb Riccardo Foschia: 
>
> Hi, 
>
> Take a look at 
> https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller section "If 
> your build wants to leave a daemon running behind..." 
>
> Greetings, 
> Riccardo 
>
> Am 26.04.2013 10:08, schrieb hezjing: 
>
> Hi 
>
> I have a job which will be run in an Linux slave. 
>
> This job will execute a shell command to start a server process which will 
> run forever. Unfortunately this process is terminated when the job is 
> finished. 
>
> When I tested this using PuTTY, the server process is still alive after I 
> logged-in and out several times. 
>
> May I know how to keep a Unix process alive after the job is completed? 
>
>
>  
>  
>  

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

Re: Exception in Guice injection of Folders plugin

[Jerry Maloney]

Good to know. Thanks for the interesting story about your dev process!
On Jul 3, 2013 7:20 AM, "Stephen Connolly" 
wrote:

> To be expected if you don't have the Jenkins Enterprise RBAC plugin. I
> think Jesse has made the exception less scary in more recent versions of
> Jenkins.
>
> In this specific case it is a historical artifact of the way the two
> plugins were developed.
>
> I developed the RBAC plugin while KK was working on the Folders plugin. I
> got finished first and cut the initial release of the RBAC plugin. That was
> finished testing and then we were doing tests on the Folders plugin when KK
> had it ready. In order to add support for RBAC into folders, we put the
> support in the Folders plugin (so as to avoid respinning the already tested
> RBAC plugin - why I don't know as RBAC at the time had >98% test coverage
> so it would have been safe to do so)... at that time the Folders and RBAC
> plugins were both Enterprise only, so 99.99% of customers would have both
> plugins installed and there would be no exception.
>
> Then the decision was made to move Folders to free (as in tell me your
> name and I'll give you this beer)... perhaps we should have moved the
> extension and the dependency over to RBAC but for maintaining backwards
> compatibility the decision was made to keep the RBAC support within
> Folders... and this scary exception is the corresponding result.
>
> TL;DR expected and perfectly normal don't worry about it
>
>
> On 3 July 2013 11:54, Jerry  wrote:
>
>> I was trying to track down a memory leak in Jenkins (or a plugin) and
>> came across the following in the log. I don't think it's related to the
>> memory leak, and I haven't seen any effects of the exception, just thought
>> someone (e.g., Stephen Connelly) might be interested in this.
>>
>> -
>>
>> Jul 02, 2013 3:55:10 PM hudson.ExtensionFinder$GuiceFinder$4$1 get
>> WARNING: Failed to instantiate. Skipping this component
>> com.google.inject.ProvisionException: Guice provision errors:
>>
>> 1) Error injecting constructor, java.lang.NoClassDefFoundError:
>> nectar/plugins/rbac/groups/ProxyGroupContainer
>>   at
>> com.cloudbees.hudson.plugins.folder.properties.FolderProxyGroupContainer$DescriptorImpl.(FolderProxyGroupContainer.java:178)
>>
>> 1 error
>> at
>> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
>> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
>>  at hudson.ExtensionFinder$GuiceFinder$4$1.get(ExtensionFinder.java:422)
>> at
>> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
>>  at
>> com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
>> at
>> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
>>  at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
>> at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391)
>>  at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382)
>> at hudson.ExtensionFinder._find(ExtensionFinder.java:151)
>>  at
>> hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:318)
>> at hudson.ExtensionList.load(ExtensionList.java:295)
>>  at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
>> at hudson.ExtensionList.getComponents(ExtensionList.java:149)
>>  at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182)
>> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
>>  at hudson.ExtensionList.iterator(ExtensionList.java:138)
>> at
>> org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:101)
>>  at
>> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)
>> 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.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
>>  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
>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
>> 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 org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
>>  at
>> org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
>> at
>> org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
>>  at
>> org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
>> at
>> org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
>>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)
>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
>>  at org.k

How to get all builds of a project via API

[Dirk Heinrichs]

Hi,

I've got a small Groovy script to get some data for all builds of a given 
project:

import hudson.model.*

def jobName = args[0]

def job = Hudson.instance.getItem(jobName)
def builds = job.getBuilds()
builds.each
{
   println 
(it.getNumber()+":"+it.getStartTimeInMillis()+":"+it.getDuration()+":"+it.getResult().toString())
}

This one works as expected. However, I only call this script from within a Perl 
script because I can't get all the data using either XML or JSON api, which 
only gives me the data for the last N builds instead of all builds, using an 
URL like 'http://server/job/MyJob/api/xml?tree=builds[number,url]'. How do I 
get the data for ALL builds using either JSON or XML?

Possible workaround: use '?tree=firstBuild[number],lastBuild[number]' and 
construct the URL for each build myself.

Thanks...

   Dirk

[cid:image003.gif@01CB3EF6.319079E0]
Dirk Heinrichs, Senior Systems Engineer, Infrastructure
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Tel: +49 2226 159 1149
Email: dirk.heinri...@recommind.com
Skype: dirk.heinrichs.recommind
www.recommind.com




http://www.recommind.com

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


<>

Re: Exception in Guice injection of XStream plugin: cannot resolve class hudson.license.LicenseManager

[Stephen Connolly]

Likely you have disabled or are missing some of the required plugins for
the folders plugin's license enforcement (the joys of this plugin being
free (as in tell me your name and I'll give you this beer)... we do ask our
management if we can make it free (as in OSS) but I have yet to see a
answer other than "we're thinking about that" so until then...)

Should not be an issue, provided once you enable the required plugins


On 3 July 2013 11:54, Jerry  wrote:

> (this is different from my last post)
>
> I was trying to track down a memory leak in Jenkins (or a plugin) and came
> across the following in the log. I don't think it's related to the memory
> leak, and I haven't seen any effects of the exception, just thought someone
> (e.g., Stephen Connelly) might be interested in this.
>
> -
>
> Jul 02, 2013 3:58:21 PM hudson.ExtensionFinder$GuiceFinder$4$1 get
> WARNING: Failed to instantiate. Skipping this component
> com.google.inject.ProvisionException: Guice provision errors:
>
> 1) Error injecting constructor,
> com.thoughtworks.xstream.mapper.CannotResolveClassException:
> hudson.license.LicenseManager
>   at hudson.license.LicenseManager.(LicenseManager.java:51)
>
> 1 error
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> at hudson.ExtensionFinder$GuiceFinder$4$1.get(ExtensionFinder.java:422)
> at
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
> at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
> at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391)
> at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382)
> at hudson.ExtensionFinder._find(ExtensionFinder.java:151)
> at
> hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:318)
> at hudson.ExtensionList.load(ExtensionList.java:295)
> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
> at hudson.ExtensionList.iterator(ExtensionList.java:138)
> at hudson.ExtensionList.get(ExtensionList.java:129)
> at hudson.license.LicenseManager.getInstanceOrDie(LicenseManager.java:235)
> at hudson.license.Reminder.findLicenseManager(Reminder.java:89)
> at hudson.license.Reminder.isDue(Reminder.java:59)
> at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
> at
> org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
> at
> org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
> at
> org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
> at
> org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
> at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
> at
> org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
> at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
> at
> hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
> at
> org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
> at
> org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:71)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
> at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
> at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
> at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
> 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
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
> at org.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44)
> at org.apache.commons.jelly

Re: Exception in Guice injection of Folders plugin

[Stephen Connolly]

To be expected if you don't have the Jenkins Enterprise RBAC plugin. I
think Jesse has made the exception less scary in more recent versions of
Jenkins.

In this specific case it is a historical artifact of the way the two
plugins were developed.

I developed the RBAC plugin while KK was working on the Folders plugin. I
got finished first and cut the initial release of the RBAC plugin. That was
finished testing and then we were doing tests on the Folders plugin when KK
had it ready. In order to add support for RBAC into folders, we put the
support in the Folders plugin (so as to avoid respinning the already tested
RBAC plugin - why I don't know as RBAC at the time had >98% test coverage
so it would have been safe to do so)... at that time the Folders and RBAC
plugins were both Enterprise only, so 99.99% of customers would have both
plugins installed and there would be no exception.

Then the decision was made to move Folders to free (as in tell me your name
and I'll give you this beer)... perhaps we should have moved the extension
and the dependency over to RBAC but for maintaining backwards compatibility
the decision was made to keep the RBAC support within Folders... and this
scary exception is the corresponding result.

TL;DR expected and perfectly normal don't worry about it


On 3 July 2013 11:54, Jerry  wrote:

> I was trying to track down a memory leak in Jenkins (or a plugin) and came
> across the following in the log. I don't think it's related to the memory
> leak, and I haven't seen any effects of the exception, just thought someone
> (e.g., Stephen Connelly) might be interested in this.
>
> -
>
> Jul 02, 2013 3:55:10 PM hudson.ExtensionFinder$GuiceFinder$4$1 get
> WARNING: Failed to instantiate. Skipping this component
> com.google.inject.ProvisionException: Guice provision errors:
>
> 1) Error injecting constructor, java.lang.NoClassDefFoundError:
> nectar/plugins/rbac/groups/ProxyGroupContainer
>   at
> com.cloudbees.hudson.plugins.folder.properties.FolderProxyGroupContainer$DescriptorImpl.(FolderProxyGroupContainer.java:178)
>
> 1 error
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> at hudson.ExtensionFinder$GuiceFinder$4$1.get(ExtensionFinder.java:422)
> at
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
> at
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
> at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
> at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391)
> at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382)
> at hudson.ExtensionFinder._find(ExtensionFinder.java:151)
> at
> hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:318)
> at hudson.ExtensionList.load(ExtensionList.java:295)
> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
> at hudson.ExtensionList.getComponents(ExtensionList.java:149)
> at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182)
> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
> at hudson.ExtensionList.iterator(ExtensionList.java:138)
> at
> org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:101)
> at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)
> 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.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
> 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
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
> 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 org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
> at
> org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
> at
> org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
> at
> org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
> at
> org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
> at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
> at winstone.

java.io.IOException: Remote call failed

[Bharathi Ramalingam]

I often get the following error when I try to launch a Job. Even though the 
slave is up and connected to the master. Following error is thrown.
Restarting the slave and re-adding it to the master solves the problem. But 
for a large environment, such things will not scale.
Has anyone came across this issue and solved it?
Any insight into this is highly appreciated.

Jenkins v 1.481
Slave connected via jnlp.
Error:
FATAL: command execution failed
java.io.IOException: Remote call on SLAVE_6 failed
 at hudson.remoting.Channel.call(Channel.java:673)
 at hudson.Launcher$RemoteLauncher.launch(Launcher.java:798)
 at hudson.Launcher$ProcStarter.start(Launcher.java:338)
 at hudson.Launcher$ProcStarter.join(Launcher.java:345)
 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:82)
 at 
hudson.plugins.envfile.EnvFileBuildWrapper.updateSlave(EnvFileBuildWrapper.java:126)
 at 
hudson.plugins.envfile.EnvFileBuildWrapper.setUp(EnvFileBuildWrapper.java:68)
 at hudson.model.Build$BuildExecution.doRun(Build.java:154)
 at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
 at hudson.model.Run.execute(Run.java:1502)
 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.NoClassDefFoundError: Could not initialize class 
jenkins.model.Jenkins$MasterComputer
 at hudson.Launcher$LocalLauncher.(Launcher.java:691)
 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:927)
 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:901)
 at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 at hudson.remoting.Request$2.run(Request.java:326)
 at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at hudson.remoting.Engine$1$1.run(Engine.java:60)
 at java.lang.Thread.run(Unknown Source)

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

Exception in Guice injection of XStream plugin: cannot resolve class hudson.license.LicenseManager

[Jerry]

(this is different from my last post)

I was trying to track down a memory leak in Jenkins (or a plugin) and came 
across the following in the log. I don't think it's related to the memory 
leak, and I haven't seen any effects of the exception, just thought someone 
(e.g., Stephen Connelly) might be interested in this.

-

Jul 02, 2013 3:58:21 PM hudson.ExtensionFinder$GuiceFinder$4$1 get
WARNING: Failed to instantiate. Skipping this component
com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, 
com.thoughtworks.xstream.mapper.CannotResolveClassException: 
hudson.license.LicenseManager
  at hudson.license.LicenseManager.(LicenseManager.java:51)

1 error
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at com.google.inject.Scopes$1$1.get(Scopes.java:59)
at hudson.ExtensionFinder$GuiceFinder$4$1.get(ExtensionFinder.java:422)
at 
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391)
at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382)
at hudson.ExtensionFinder._find(ExtensionFinder.java:151)
at 
hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:318)
at hudson.ExtensionList.load(ExtensionList.java:295)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
at hudson.ExtensionList.iterator(ExtensionList.java:138)
at hudson.ExtensionList.get(ExtensionList.java:129)
at hudson.license.LicenseManager.getInstanceOrDie(LicenseManager.java:235)
at hudson.license.Reminder.findLicenseManager(Reminder.java:89)
at hudson.license.Reminder.isDue(Reminder.java:59)
at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at 
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at 
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at 
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at 
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at 
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:71)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
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 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at org.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at 
org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
at 
org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
at 
org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
at 
org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.

Exception in Guice injection of Folders plugin

[Jerry]

I was trying to track down a memory leak in Jenkins (or a plugin) and came 
across the following in the log. I don't think it's related to the memory 
leak, and I haven't seen any effects of the exception, just thought someone 
(e.g., Stephen Connelly) might be interested in this.

-

Jul 02, 2013 3:55:10 PM hudson.ExtensionFinder$GuiceFinder$4$1 get
WARNING: Failed to instantiate. Skipping this component
com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting constructor, java.lang.NoClassDefFoundError: 
nectar/plugins/rbac/groups/ProxyGroupContainer
  at 
com.cloudbees.hudson.plugins.folder.properties.FolderProxyGroupContainer$DescriptorImpl.(FolderProxyGroupContainer.java:178)

1 error
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at com.google.inject.Scopes$1$1.get(Scopes.java:59)
at hudson.ExtensionFinder$GuiceFinder$4$1.get(ExtensionFinder.java:422)
at 
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391)
at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382)
at hudson.ExtensionFinder._find(ExtensionFinder.java:151)
at 
hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:318)
at hudson.ExtensionList.load(ExtensionList.java:295)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
at hudson.ExtensionList.getComponents(ExtensionList.java:149)
at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
at hudson.ExtensionList.iterator(ExtensionList.java:138)
at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:101)
at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)
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.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
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 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
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 org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at 
org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
at 
org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
at 
org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
at 
org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at 
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227)
at winstone.RequestHandlerThread.run(RequestHandlerThr

Re: How to keep Unix process alive after job is completed?

[John Vacz]

We have a job executing a shell script (on a slave) to restart one dev 
appserver on a remote server if it does not work properly (dont bother 
why its not working):


  # BUILD_ID=dontKillMe
  ssh user@some.remote.server exec 
/path/to/appserver/force_restart_script arg1


The "force_restart_script" on the *remote* server doing the following:

  # find and kill the old appserver process
  kill_appserver_script arg1
  # start appserver with specified argument
  /path/to/appserver/start_appserver_script arg1

At the end, the old appserver process was killed, and the new appserver 
process was also terminated. How can i keep this from happening? The 
BUILD_ID=dontKillMe in job configureation doesn't seem to work (that 
would only keep the ssh from being terminated on the slave, right?), or 
I should actually set the BUILD_ID in the remote ssh shell?


Any help is very much appreciated!

-jv

Am 26.04.2013 10:16, schrieb Riccardo Foschia:

Hi,

Take a look at 
https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller section 
"If your build wants to leave a daemon running behind..."


Greetings,
Riccardo

Am 26.04.2013 10:08, schrieb hezjing:

Hi

I have a job which will be run in an Linux slave.

This job will execute a shell command to start a server process which 
will

run forever. Unfortunately this process is terminated when the job is
finished.

When I tested this using PuTTY, the server process is still alive 
after I

logged-in and out several times.

May I know how to keep a Unix process alive after the job is completed?






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

Re: HELP! Jenkins no longer connects to Subversion (svn: REPORT of /svn/repo_name/!svn/vcc/default: 500 Internal Server Error)

[Masariello]

Yes, the clocks are in sync. And the checkout started to work again.

Unfortunately I did not think of checking the clocks yesterday. Will 
certainly do it next time I get the problem.

Thanks for the prompt feedback! 


On Wednesday, July 3, 2013 8:41:55 AM UTC+1, matthew...@diamond.ac.uk wrote:
>
>  Are the clocks on the Jenkins machine and the subversion server in sync 
> (e.g. via ntp)? They need to be.
>
> Matthew
>
>  
>   
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Masariello
> *Sent:* 02 July 2013 21:39
> *To:* jenkins...@googlegroups.com 
> *Subject:* HELP! Jenkins no longer connects to Subversion (svn: REPORT of 
> /svn/repo_name/!svn/vcc/default: 500 Internal Server Error)
>  
>  
>
> I've been running a Jenkins 1.480.x + VisualSvn 2.5.x since Nov 2012.
>  
>  
>  
> A few days ago we started to experience the exception below ('500 
> Internal Server Error'). For a few times the problem went away after a 
> reboot. But today everything started to fail ALWAYS.
>  
>  
>  
> This started to happen completely out of the blue, with Jenkins Subversion 
> plugin v1.39. Upgrading to v1.50 did not help.
>  
>  
>  
> Every time I get the exception, the Subversion server logs and event 
> saying "Could not access revision times. [500.#0]".
>  
>  
>  
> The svn polling log shows that Jenkins is successfully detecting new 
> commits in the repositories. The problem below happens during checkout.
>  
>  
>  
> The Subversion server seems to be working absolutely fine, both via simple 
> http, and via TortoiseSvn.
>  
>  
>  
> I've tried
>  
>- upgrading to VisualSvn 2.6, with no change.
>- having Jenkins access svn via the server hostname, rather than its 
>DNS alias (causing Jenkins to re-auth)
>- wiping all the workspaces
>
>  Nothing seems to work.
>  
>  
>  
> Has anyone else seen this before?
>   
>  
>  
> Thanks in advance!
>   
>  
>
> --  
>
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not 
> use, copy, retain, distribute or disclose the information in or attached to 
> the e-mail.
> Any opinions expressed within this e-mail are those of the individual and 
> not necessarily of Diamond Light Source Ltd. 
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England 
> and Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>  
>
>

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

A strange issues about master connecting slave

[Zhouping Liu]

Hello All,

I met the below issues when I added a new node to jenkins:

- snip ---

_=/etc/bashrc
[07/03/13 03:13:30] [SSH] Checking java version of java
[07/03/13 03:13:30] [SSH] java -version returned 1.7.0_03.
[07/03/13 03:13:30] [SSH] Starting sftp client.
[07/03/13 03:13:30] [SSH] Copying latest slave.jar...
[07/03/13 03:13:30] [SSH] Copied 326,006 bytes.
Expanded the channel window size to 4MB
[07/03/13 03:13:30] [SSH] Starting slave process: cd '/home/jenkins'
&& java  -jar slave.jar
<===[JENKINS REMOTING CAPACITY]===>channel started
Exception in thread "Ping thread for channel
hudson.remoting.Channel@7c067f03:channel"
java.security.ProviderException: Error parsing configuration
at sun.security.pkcs11.Config.getConfig(Config.java:88)
at sun.security.pkcs11.SunPKCS11.(SunPKCS11.java:128)
at sun.security.pkcs11.SunPKCS11.(SunPKCS11.java:103)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:224)
at sun.security.jca.ProviderConfig$2.run(ProviderConfig.java:206)
at java.security.AccessController.doPrivileged(Native Method)
at 
sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:206)
at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:187)
at sun.security.jca.ProviderList.getProvider(ProviderList.java:232)
at sun.security.jca.ProviderList.getService(ProviderList.java:330)
at sun.security.jca.GetInstance.getInstance(GetInstance.java:157)
at java.security.Security.getImpl(Security.java:695)
at java.security.MessageDigest.getInstance(MessageDigest.java:159)
at 
java.io.ObjectStreamClass.computeDefaultSUID(ObjectStreamClass.java:1782)
at java.io.ObjectStreamClass.access$100(ObjectStreamClass.java:69)
at java.io.ObjectStreamClass$1.run(ObjectStreamClass.java:247)
at java.io.ObjectStreamClass$1.run(ObjectStreamClass.java:245)
at java.security.AccessController.doPrivileged(Native Method)
at 
java.io.ObjectStreamClass.getSerialVersionUID(ObjectStreamClass.java:244)
at java.io.ObjectStreamClass.writeNonProxy(ObjectStreamClass.java:709)
ERROR:  at 
java.io.ObjectOutputStream.writeClassDescriptor(ObjectOutputStream.java:664)ERROR:
Connection terminated
Unexpected error in launching a slave. This is probably a bug in Jenkins.

at 
java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1269)
at 
java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1227)
at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1306)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1170)
at 
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
at 
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:438)
at java.lang.Throwable.writeObject(Throwable.java:984)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:975)java.io.InvalidClassException
:
[Ljava.lang.StackTraceElement;; serializable and externalizable flags
conflict
at 
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1480)

at java.io.ObjectStreamClass.readNonProxy(ObjectStreamClass.java:672)

hudson.remoting.RequestAbortedException:
hudson.remoting.RequestAbortedException:
java.io.InvalidClassException: [Ljava.lang.StackTraceElement;;
serializable and externalizable flags conflict

 snip ---

Did any one meet the same issue, and can any one tell me how to resolve
such issue?

Thanks,
Zhouping

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

howto redirect file content to ANT console to follow a build

[Markus Bauer-Sommerfeld]

I have setup a Jenkins job which calls an ANT script. This ANT-script calls 
Matlab to codegenerate and compile Software. Matlab writes continously 
while working to a logfile. This target takes about 90--150mins.

Is it possible to redirect the content of the matlab logfile to the ANT 
console to follow the Jenkins job?

My current solution loads the logfile after finishing the task which calls 
matlab, so I have no possibility to get information whats up in the running 
matlab process:

[...]

  

  



[...]

Thanks in advance for a reply
Markus

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

RE: HELP! Jenkins no longer connects to Subversion (svn: REPORT of /svn/repo_name/!svn/vcc/default: 500 Internal Server Error)

[Matthew.Webber]

Are the clocks on the Jenkins machine and the subversion server in sync (e.g. 
via ntp)? They need to be.
Matthew

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Masariello
Sent: 02 July 2013 21:39
To: jenkinsci-users@googlegroups.com
Subject: HELP! Jenkins no longer connects to Subversion (svn: REPORT of 
/svn/repo_name/!svn/vcc/default: 500 Internal Server Error)

I've been running a Jenkins 1.480.x + VisualSvn 2.5.x since Nov 2012.

A few days ago we started to experience the exception below ('500 Internal 
Server Error'). For a few times the problem went away after a reboot. But today 
everything started to fail ALWAYS.

This started to happen completely out of the blue, with Jenkins Subversion 
plugin v1.39. Upgrading to v1.50 did not help.

Every time I get the exception, the Subversion server logs and event saying 
"Could not access revision times. [500.#0]".

The svn polling log shows that Jenkins is successfully detecting new commits in 
the repositories. The problem below happens during checkout.

The Subversion server seems to be working absolutely fine, both via simple 
http, and via TortoiseSvn.

I've tried

  *   upgrading to VisualSvn 2.6, with no change.
  *   having Jenkins access svn via the server hostname, rather than its DNS 
alias (causing Jenkins to re-auth)
  *   wiping all the workspaces
Nothing seems to work.

Has anyone else seen this before?

Thanks in advance!



-- 

This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.

Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 

Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.

Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

 







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

Disable fingerprinting? (1.509.1 LTS)

[Steffen Breitbach]

Hi everyone!

We don't use fingerprinting in our projects. Therefore I'd like to
disable fingerprinting globally. Is there a way to do so?

Regards
  Steffen

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