Re: groovy post build stops to work and no emails are sent

[Slide]

That error really isn't important, it shouldn't be marked SEVERE, it's not
actually an error. I don't think it relates to what you are seeing.

On Fri, Oct 24, 2014 at 9:40 PM, Sam T  wrote:

> I am getting conflicting results now. After removing the groovy postbuild
> task, one of my jobs sends email but another job keeps failing with this
> error message.
> So, perhaps this is a base groovy error with the extended-email plugin
> after all. Here is the error message.
>
> Oct 24, 2014 8:53:22 PM
> hudson.plugins.emailext.plugins.content.ScriptContent createEngine
> SEVERE: Exception on init file: java.io.FileNotFoundException:
> /home/jenkins/email-templates/groovy/init.groovy (No such file or directory)
>
> Once again, if anyone has noticed these symptoms and knows of a
> workaround, please post. Thanks.
>
>
>
> On Friday, October 24, 2014 1:46:29 PM UTC-7, Sam T wrote:
>>
>> My apologies for not providing more detailed information. My jenkins is
>> at version 1.494 . This is the way the job is setup. This job is created
>> using multijob plugin where you can fire off  other jobs and chain them
>> together.
>> There are three postbuild actions configured for this job in this exact
>> order:
>>
>> 1) First post build is using groovypost build and it has a small code
>> that sets the status of the top level job itself. The groovy postbuild
>> plugin is at version 1.7 and here is the code in the job that it executes:
>> if(manager.logContains(".*FAILURE.*")) {
>> manager.buildFailure()
>> }
>>
>> else if(manager.logContains(".*UNSTABLE.*")) {
>> manager.buildUnstable()
>> }
>>
>> 2) the next post build action is "Aggregate downstream post build
>> results"  which I believe is built into jenkins itself and there is no
>> plugin for it.
>>
>> 3) the last post build action is an extended email plugin that executes
>> code and generates email. This plugin is at version 2.21
>>
>> I just performed an experiment. I removed the first postbuild action  for
>> the groovy postbuild in a sample test job and I noticed that emails are
>> generated again.
>> So, based on this experiment, the issue seems to be with the very first
>> post build action which is excuted by the groovy postbuild plugin.
>> My theory is that once the groovy postbuild plugin fails, the other two
>> post build actions are ignored and no email is sent out by jenkins.
>>
>> If anyone has seen a similar problem, please let me know if you have
>> found a solution, a workaround or a way to debug the issue. Thanks.
>>
>>
>>
>> On Friday, October 24, 2014 1:07:30 PM UTC-7, slide wrote:
>>>
>>> What version of email-ext do you have installed?
>>>
>>> On Fri, Oct 24, 2014 at 11:31 AM, Sam T  wrote:
>>>
 I have inherited a system that runs groovy to generate emails as a post
 build action. The system has not been changed at all and the groovy
 postbuild action and email has been working without any errors for over a
 year.
 All of a sudden emails stop being sent from those jobs that have groovy
 post build email generation. I have seen the following error in the jenkins
 log:

 SEVERE: Exception on init file: java.io.FileNotFoundException:
 /home/jenkins/email-templates/groovy/init.groovy (No such file or
 directory)
 Warning: Caused by: java.lang.AssertionError: class
 org.jvnet.hudson.plugins.groovypostbuild.GroovyScriptPath is missing
 its descriptor in public java.util.List org.jvnet.hudson.plugins.
 groovypostbuild.GroovyPostbuildRecorder.getClasspath(). See
 https://wiki.jenkins-ci.org/display/JENKINS/My+class+is+
 missing+descriptor at hudson.model.Descriptor$PropertyType.
 getItemTypeDescriptorOrDie(Descriptor.java:202)

 The file /home/jenkins/email-templates/groovy/init.groovy never
 existed on this server. I have examined all of our full backups of the
 /home/jenkins directory. But I still see jenkins logs a SEVERE error which
 is strange.
 The Java stack trace is a "warning" but that may point to an issue.

 I have researched and I have seen posts that claim
 /home/jenkins/email-templates/groovy/init.groovy is not even needed
 for groovy postbuild and email generation.
 I copied ./plugins/email-ext/WEB-INF/classes/hudson/plugins/
 emailext/templates/groovy/foo.init.groovy into
 /home/jenkins/email-templates/groovy/init.groovy and there is still no
 email.
 I have seen this bug regarding the groovy postbuild plugin
 https://issues.jenkins-ci.org/browse/JENKINS-13024
 I will upgrade to version 1.8 which has fixed a similar problem and see
 what happens.

 My question is: has anyone run into a similar issue and what was the
 steps to fix it?

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

Re: groovy post build stops to work and no emails are sent

[Sam T]

I am getting conflicting results now. After removing the groovy postbuild 
task, one of my jobs sends email but another job keeps failing with this 
error message.
So, perhaps this is a base groovy error with the extended-email plugin 
after all. Here is the error message.

Oct 24, 2014 8:53:22 PM 
hudson.plugins.emailext.plugins.content.ScriptContent createEngine
SEVERE: Exception on init file: java.io.FileNotFoundException: 
/home/jenkins/email-templates/groovy/init.groovy (No such file or directory)

Once again, if anyone has noticed these symptoms and knows of a workaround, 
please post. Thanks.


On Friday, October 24, 2014 1:46:29 PM UTC-7, Sam T wrote:
>
> My apologies for not providing more detailed information. My jenkins is at 
> version 1.494 . This is the way the job is setup. This job is created using 
> multijob plugin where you can fire off  other jobs and chain them together.
> There are three postbuild actions configured for this job in this exact 
> order:
>
> 1) First post build is using groovypost build and it has a small code that 
> sets the status of the top level job itself. The groovy postbuild plugin is 
> at version 1.7 and here is the code in the job that it executes:
> if(manager.logContains(".*FAILURE.*")) {
> manager.buildFailure()
> }
>
> else if(manager.logContains(".*UNSTABLE.*")) {
> manager.buildUnstable()
> }
>
> 2) the next post build action is "Aggregate downstream post build 
> results"  which I believe is built into jenkins itself and there is no 
> plugin for it.
>
> 3) the last post build action is an extended email plugin that executes 
> code and generates email. This plugin is at version 2.21
>
> I just performed an experiment. I removed the first postbuild action  for 
> the groovy postbuild in a sample test job and I noticed that emails are 
> generated again.
> So, based on this experiment, the issue seems to be with the very first 
> post build action which is excuted by the groovy postbuild plugin.
> My theory is that once the groovy postbuild plugin fails, the other two 
> post build actions are ignored and no email is sent out by jenkins.
>
> If anyone has seen a similar problem, please let me know if you have found 
> a solution, a workaround or a way to debug the issue. Thanks.
>
>
>
> On Friday, October 24, 2014 1:07:30 PM UTC-7, slide wrote:
>>
>> What version of email-ext do you have installed?
>>
>> On Fri, Oct 24, 2014 at 11:31 AM, Sam T  wrote:
>>
>>> I have inherited a system that runs groovy to generate emails as a post 
>>> build action. The system has not been changed at all and the groovy 
>>> postbuild action and email has been working without any errors for over a 
>>> year.
>>> All of a sudden emails stop being sent from those jobs that have groovy 
>>> post build email generation. I have seen the following error in the jenkins 
>>> log:
>>>
>>> SEVERE: Exception on init file: java.io.FileNotFoundException: 
>>> /home/jenkins/email-templates/groovy/init.groovy (No such file or directory)
>>> Warning: Caused by: java.lang.AssertionError: class 
>>> org.jvnet.hudson.plugins.groovypostbuild.GroovyScriptPath is missing its 
>>> descriptor in public java.util.List 
>>> org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.getClasspath().
>>>  
>>> See 
>>> https://wiki.jenkins-ci.org/display/JENKINS/My+class+is+missing+descriptor  
>>>
>>> at 
>>> hudson.model.Descriptor$PropertyType.getItemTypeDescriptorOrDie(Descriptor.java:202)
>>>
>>> The file /home/jenkins/email-templates/groovy/init.groovy never existed 
>>> on this server. I have examined all of our full backups of the 
>>> /home/jenkins directory. But I still see jenkins logs a SEVERE error which 
>>> is strange.
>>> The Java stack trace is a "warning" but that may point to an issue.
>>>
>>> I have researched and I have seen posts that claim 
>>> /home/jenkins/email-templates/groovy/init.groovy is not even needed for 
>>> groovy postbuild and email generation.
>>> I copied 
>>> ./plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/templates/groovy/foo.init.groovy
>>>  
>>> into /home/jenkins/email-templates/groovy/init.groovy and there is still no 
>>> email.
>>> I have seen this bug regarding the groovy postbuild plugin
>>> https://issues.jenkins-ci.org/browse/JENKINS-13024
>>> I will upgrade to version 1.8 which has fixed a similar problem and see 
>>> what happens.
>>>
>>> My question is: has anyone run into a similar issue and what was the 
>>> steps to fix it?
>>>
>>> -- 
>>> 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/d/optout.
>>>
>>
>>
>>
>> -- 
>> Website: http://earl-of-code.com 
>>
>

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

Re: groovy post build stops to work and no emails are sent

[Sam T]

My apologies for not providing more detailed information. My jenkins is at 
version 1.494 . This is the way the job is setup. This job is created using 
multijob plugin where you can fire off  other jobs and chain them together.
There are three postbuild actions configured for this job in this exact 
order:

1) First post build is using groovypost build and it has a small code that 
sets the status of the top level job itself. The groovy postbuild plugin is 
at version 1.7 and here is the code in the job that it executes:
if(manager.logContains(".*FAILURE.*")) {
manager.buildFailure()
}

else if(manager.logContains(".*UNSTABLE.*")) {
manager.buildUnstable()
}

2) the next post build action is "Aggregate downstream post build results"  
which I believe is built into jenkins itself and there is no plugin for it.

3) the last post build action is an extended email plugin that executes 
code and generates email. This plugin is at version 2.21

I just performed an experiment. I removed the first postbuild action  for 
the groovy postbuild in a sample test job and I noticed that emails are 
generated again.
So, based on this experiment, the issue seems to be with the very first 
post build action which is excuted by the groovy postbuild plugin.
My theory is that once the groovy postbuild plugin fails, the other two 
post build actions are ignored and no email is sent out by jenkins.

If anyone has seen a similar problem, please let me know if you have found 
a solution, a workaround or a way to debug the issue. Thanks.



On Friday, October 24, 2014 1:07:30 PM UTC-7, slide wrote:
>
> What version of email-ext do you have installed?
>
> On Fri, Oct 24, 2014 at 11:31 AM, Sam T 
> > wrote:
>
>> I have inherited a system that runs groovy to generate emails as a post 
>> build action. The system has not been changed at all and the groovy 
>> postbuild action and email has been working without any errors for over a 
>> year.
>> All of a sudden emails stop being sent from those jobs that have groovy 
>> post build email generation. I have seen the following error in the jenkins 
>> log:
>>
>> SEVERE: Exception on init file: java.io.FileNotFoundException: 
>> /home/jenkins/email-templates/groovy/init.groovy (No such file or directory)
>> Warning: Caused by: java.lang.AssertionError: class 
>> org.jvnet.hudson.plugins.groovypostbuild.GroovyScriptPath is missing its 
>> descriptor in public java.util.List 
>> org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.getClasspath().
>>  
>> See 
>> https://wiki.jenkins-ci.org/display/JENKINS/My+class+is+missing+descriptor   
>>   
>> at 
>> hudson.model.Descriptor$PropertyType.getItemTypeDescriptorOrDie(Descriptor.java:202)
>>
>> The file /home/jenkins/email-templates/groovy/init.groovy never existed 
>> on this server. I have examined all of our full backups of the 
>> /home/jenkins directory. But I still see jenkins logs a SEVERE error which 
>> is strange.
>> The Java stack trace is a "warning" but that may point to an issue.
>>
>> I have researched and I have seen posts that claim 
>> /home/jenkins/email-templates/groovy/init.groovy is not even needed for 
>> groovy postbuild and email generation.
>> I copied 
>> ./plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/templates/groovy/foo.init.groovy
>>  
>> into /home/jenkins/email-templates/groovy/init.groovy and there is still no 
>> email.
>> I have seen this bug regarding the groovy postbuild plugin
>> https://issues.jenkins-ci.org/browse/JENKINS-13024
>> I will upgrade to version 1.8 which has fixed a similar problem and see 
>> what happens.
>>
>> My question is: has anyone run into a similar issue and what was the 
>> steps to fix it?
>>
>> -- 
>> 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/d/optout.
>>
>
>
>
> -- 
> 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/d/optout.

Re: groovy post build stops to work and no emails are sent

[Slide]

What version of email-ext do you have installed?

On Fri, Oct 24, 2014 at 11:31 AM, Sam T  wrote:

> I have inherited a system that runs groovy to generate emails as a post
> build action. The system has not been changed at all and the groovy
> postbuild action and email has been working without any errors for over a
> year.
> All of a sudden emails stop being sent from those jobs that have groovy
> post build email generation. I have seen the following error in the jenkins
> log:
>
> SEVERE: Exception on init file: java.io.FileNotFoundException:
> /home/jenkins/email-templates/groovy/init.groovy (No such file or directory)
> Warning: Caused by: java.lang.AssertionError: class
> org.jvnet.hudson.plugins.groovypostbuild.GroovyScriptPath is missing its
> descriptor in public java.util.List
> org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.getClasspath().
> See
> https://wiki.jenkins-ci.org/display/JENKINS/My+class+is+missing+descriptor
> at
> hudson.model.Descriptor$PropertyType.getItemTypeDescriptorOrDie(Descriptor.java:202)
>
> The file /home/jenkins/email-templates/groovy/init.groovy never existed on
> this server. I have examined all of our full backups of the /home/jenkins
> directory. But I still see jenkins logs a SEVERE error which is strange.
> The Java stack trace is a "warning" but that may point to an issue.
>
> I have researched and I have seen posts that claim
> /home/jenkins/email-templates/groovy/init.groovy is not even needed for
> groovy postbuild and email generation.
> I copied
> ./plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/templates/groovy/foo.init.groovy
> into /home/jenkins/email-templates/groovy/init.groovy and there is still no
> email.
> I have seen this bug regarding the groovy postbuild plugin
> https://issues.jenkins-ci.org/browse/JENKINS-13024
> I will upgrade to version 1.8 which has fixed a similar problem and see
> what happens.
>
> My question is: has anyone run into a similar issue and what was the steps
> to fix it?
>
> --
> 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/d/optout.
>



-- 
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/d/optout.

groovy post build stops to work and no emails are sent

[Sam T]

I have inherited a system that runs groovy to generate emails as a post 
build action. The system has not been changed at all and the groovy 
postbuild action and email has been working without any errors for over a 
year.
All of a sudden emails stop being sent from those jobs that have groovy 
post build email generation. I have seen the following error in the jenkins 
log:

SEVERE: Exception on init file: java.io.FileNotFoundException: 
/home/jenkins/email-templates/groovy/init.groovy (No such file or directory)
Warning: Caused by: java.lang.AssertionError: class 
org.jvnet.hudson.plugins.groovypostbuild.GroovyScriptPath is missing its 
descriptor in public java.util.List 
org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.getClasspath().
 
See 
https://wiki.jenkins-ci.org/display/JENKINS/My+class+is+missing+descriptor  
   
at 
hudson.model.Descriptor$PropertyType.getItemTypeDescriptorOrDie(Descriptor.java:202)

The file /home/jenkins/email-templates/groovy/init.groovy never existed on 
this server. I have examined all of our full backups of the /home/jenkins 
directory. But I still see jenkins logs a SEVERE error which is strange.
The Java stack trace is a "warning" but that may point to an issue.

I have researched and I have seen posts that claim 
/home/jenkins/email-templates/groovy/init.groovy is not even needed for 
groovy postbuild and email generation.
I copied 
./plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/templates/groovy/foo.init.groovy
 
into /home/jenkins/email-templates/groovy/init.groovy and there is still no 
email.
I have seen this bug regarding the groovy postbuild plugin
https://issues.jenkins-ci.org/browse/JENKINS-13024
I will upgrade to version 1.8 which has fixed a similar problem and see 
what happens.

My question is: has anyone run into a similar issue and what was the steps 
to fix it?

-- 
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/d/optout.

Re: Allowing a job to run (triggered manually) only if a specific list of jobs are "blue" successful

[Christopher Orr]

On 09/10/14 15:38, Alon Nisser wrote:

Is there a way to achieve that? getting the status of other jobs and
checking if last run was "success"?

I don't want to automatically run this deployment job on the upstream
success, but to trigger this manually. but still safeguard by checking
upstream (multiple) success


You try using the Promoted Builds Plugin as described in this Stack 
Overflow answer:

http://stackoverflow.com/a/9013233/234938

--
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/d/optout.

Re: Deploy Plugin 1.10 - deploy to Jboss 7.x - Cannot locate the JBoss connector classes

[Klaus Wienert]

I can acc the Problem. Here is my stacktrace on jenkins 1.552


ERROR: Publisher hudson.plugins.deploy.DeployPublisher aborted due to 
exceptionorg.codehaus.cargo.container.ContainerException 
:
 Failed to create deployer with implementation class 
org.codehaus.cargo.container.jboss.JBoss7xRemoteDeployer for the parameters 
(container [id = [jboss7x]], deployer type [remote]).
at 
org.codehaus.cargo.generic.spi.AbstractGenericHintFactory.createImplementation(AbstractGenericHintFactory.java:154)
 

at 
org.codehaus.cargo.generic.spi.AbstractIntrospectionGenericHintFactory.createImplementation(AbstractIntrospectionGenericHintFactory.java:93)
 

at 
org.codehaus.cargo.generic.deployer.DefaultDeployerFactory.createDeployer(DefaultDeployerFactory.java:141)
 

at 
org.codehaus.cargo.generic.deployer.DefaultDeployerFactory.createDeployer(DefaultDeployerFactory.java:161)
 

at 
hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:61)
 

at 
hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:116)
 

at 
hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:103)
 

at hudson.FilePath.act(FilePath.java:914) 

at hudson.FilePath.act(FilePath.java:887) 

at 
hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:103)
 

at 
hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:61) 

at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
 

at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030)
 

at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) 

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

at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) 

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

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

Caused by: java.lang.reflect.InvocationTargetException 

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.Delegatin

hudson remoting: IllegalStateException

[James Green]

I got the following stacktrace as my build "aborted". I manually invoked
the build again and it worked fine. Any ideas?

[INFO] All coverage checks have been met.
java.lang.reflect.InvocationTargetException
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:606)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178)
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:606)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:136)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:71)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.Error: Unable to load resource
hudson/plugins/analysis/Messages.properties
at 
hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:380)
at java.lang.ClassLoader.getResource(ClassLoader.java:1147)
at java.lang.Class.getResource(Class.java:2147)
at 
org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:83)
at 
org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102)
at 
org.jvnet.localizer.ResourceBundleHolder.format(ResourceBundleHolder.java:139)
at 
hudson.plugins.analysis.Messages.FilesParser_Error_NoPermission(Messages.java:437)
at 
hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:269)
at 
hudson.plugins.analysis.core.FilesParser.parseSingleFile(FilesParser.java:239)
at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:198)
at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)
at hudson.FilePath.act(FilePath.java:918)
at hudson.FilePath.act(FilePath.java:896)
at 
hudson.plugins.checkstyle.CheckStyleReporter.perform(CheckStyleReporter.java:126)
at 
hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:301)
at 
hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634)
at 
hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:615)
at 
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
at 
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at 
org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:117)
... 21 more
Caused by: java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Invalid object ID 2 iota=18
at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:75)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at 
hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:372)
... 49 more
Caused by: java.lang.IllegalStateException: Invalid object ID 2 iota=18
   

Build parameter not passing through

[James Green]

Jenkins 1.585
Maven Integration Plugin 1.7

Part of my pom uses maven-enforcer-plugin to requireEnvironmentVariable,
failing if it's not found.

I thought by providing this as a build parameter (
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build) I would
satisfy the build. But it's not passed through at all.

I fear I now have to set this in the "Goals and options" of the project
config screen, which I didn't want to do for security reasons.

Am I missing something?

James

-- 
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/d/optout.

Retrieve user in System Groovy Choice Parameter

[Sascha.Retter]

Hello Everybody,

we need to identify the currently logged-in user in an "Extensible Choice 
Parameter" with Choice Provider "System Groovy Choice Parameter". We tried the 
following:

*   User.current()
*   Jenkins.getAuthentication()
*   Build.getCause ... which works in a build step but not in an Extensible 
Choice Parameter

We need the user or more exactly the groups the user is member of to calculate 
what is displayed in the Choice Parameter dropdown. Is there a way to retrieve 
the user?

Thanks & best regards,

Sascha Retter


-- 
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/d/optout.