date:20130624















































Oleg Nenashev
 created  JENKINS-18465


Invalid behavior of p4 Run script installer















Issue Type:


Bug



Affects Versions:


current



Assignee:


Rob Petti



Components:


perforce



Created:


24/Jun/13 8:25 AM



Description:


Hello, I've experienced several issues with Perforce Tool Installer:
1) Seems that perforce plugin ignores script installer on Windows
2) In case of Linux, P4 plugin considers “Tool Home” as a full path to executable (in common, this field is being used to specify path to tool’s ROOT directory)





Project:


Jenkins



Priority:


Major



Reporter:


Oleg Nenashev

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Srikanth Tirukovalluru
 created  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















Issue Type:


Bug



Assignee:


Raphael CHAUMIER



Attachments:


Jenkins_WeblogicPluginError.docx



Components:


weblogic-deployer



Created:


24/Jun/13 8:27 AM



Description:


When i am trying to configure weblogic deployment plugin, i am always getting an error page. Please find the attachment below to know the error trace.
I need to know from where 'Stage Mode' options in 'WebLogic configuration' section are populated? There is no configuration file where i can mention the modes.




Due Date:


24/Jun/13 12:00 AM




Environment:


Windows, Java, weblogic 11g application server, 




Project:


Jenkins



Labels:


plugin




Priority:


Blocker



Reporter:


Srikanth Tirukovalluru

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [integrity-plugin] (JENKINS-14593) Several crash during project synchronization













































 
Kai Burjack
 edited a comment on  JENKINS-14593


Several crash during project synchronization
















I can confirm that "try3" (no files in workspace) happens with me now almost at all times.
Sometimes, a single file in the project root is checkedout. Other times no files are checkedout at all.
But the directory structure is always created (but just no files downloaded).

I tried this with the remote integration point (via HTTP protocol) and the local integration point (with a locally running client) using the RMI beep protocol. Same result in both cases.
When using the CLI interface over bash directly "si createsandbox", everything works fine!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [integrity-plugin] (JENKINS-14593) Several crash during project synchronization















































Kai Burjack
 commented on  JENKINS-14593


Several crash during project synchronization















I can confirm that "try3" (no files in workspace) happens with me now almost at all times.
Sometimes, a single file in the project root is checkedout. Other times no files are checkedout at all.
But the directly structure is always created (but just no files downloaded).

I tried this with the remote integration point (via HTTP protocol) and the local integration point (with a locally running client) using the RMI beep protocol. Same result in both cases.
When using the CLI interface over bash directly "si createsandbox", everything works fine!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18466) Jenkins checks wrong disks for available diskspace

2013-06-24 Thread f...@br0tbox.de (JIRA)
















































Timm H
 resolved  JENKINS-18466 as Not A Defect


Jenkins checks wrong disks for available diskspace
















Change By:


Timm H
(24/Jun/13 8:37 AM)




Status:


Open
Resolved





Resolution:


NotADefect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18466) Jenkins checks wrong disks for available diskspace

2013-06-24 Thread f...@br0tbox.de (JIRA)















































Timm H
 commented on  JENKINS-18466


Jenkins checks wrong disks for available diskspace















User error. After bringing the node back online, it correctly read the availavle disk space.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-18462) Add support for URL trigger/Github Push trigger plugin

2013-06-24 Thread jabbrw...@gmail.com (JIRA)















































Jens Hausherr
 updated  JENKINS-18462


Add support for URL trigger/Github Push trigger plugin
















Change By:


Jens Hausherr
(24/Jun/13 8:41 AM)




Summary:


AddsupportforURLtrigger
/GithubPushtrigger
plugin





Description:


SupportfortheURLtriggerpluginwouldbeniceasitwouldenablebasicdependencytriggeringfornon-mavenprojects.
(CurrentlyusingitforSBTprojecs).Alsoaddingsupportforgithubpushnotifications(asitistrivialtoadd)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-18465) Invalid behavior of p4 Run script installer















































Oleg Nenashev
 updated  JENKINS-18465


Invalid behavior of p4 Run script installer
















Change By:


Oleg Nenashev
(24/Jun/13 8:43 AM)




Description:


Hello,Iveexperiencedseveralissueswith
Perforce
ToolInstaller
plugindoesntcorrectlyincaseofScriptinstaller
:1)SeemsthatperforcepluginignoresscriptinstalleronWindows2)IncaseofLinux,P4pluginconsiders“ToolHome”asafullpathtoexecutable(incommon,thisfieldisbeingusedtospecifypathtotool’sROOTdirectory)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18441) Maven 2 jobs fail (exception in MavenFingerprinter)















































K P
 updated  JENKINS-18441


Maven 2 jobs fail (exception in MavenFingerprinter)
















Change By:


K P
(24/Jun/13 8:43 AM)




Assignee:


MarcSanfacon
UlliHafner





Component/s:


findbugs



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18441) Maven 2 jobs fail (exception in MavenFingerprinter)

2013-06-24 Thread ullrich.haf...@gmail.com (JIRA)















































Ulli Hafner
 updated  JENKINS-18441


Maven 2 jobs fail (exception in MavenFingerprinter)
















Why did you assign this issue to me?





Change By:


Ulli Hafner
(24/Jun/13 8:48 AM)




Assignee:


UlliHafner
MarcSanfacon





Component/s:


findbugs



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18441) Maven 2 jobs fail (exception in MavenFingerprinter)

2013-06-24 Thread ullrich.haf...@gmail.com (JIRA)















































Ulli Hafner
 updated  JENKINS-18441


Maven 2 jobs fail (exception in MavenFingerprinter)
















Change By:


Ulli Hafner
(24/Jun/13 8:48 AM)




Assignee:


MarcSanfacon



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18441) Maven 2 jobs fail (exception in MavenFingerprinter)















































K P
 commented on  JENKINS-18441


Maven 2 jobs fail (exception in MavenFingerprinter)















Update:

I've played around some more with various configurations:

When I disable Findbugs reporting, I still get the above stack trace and warnings, BUT, at the end, the build does not fail.

I've also tried switching to Maven 3 (Maven 3.0.5). Without Findbugs: no stack trace, and build succeeds. With Findbugs: 

[INFO] Generating "Dependencies" report--- maven-project-info-reports-plugin:2.6
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	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:174)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IncompatibleClassChangeError: Implementing class
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:705)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:759)
	at sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:282)
	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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Raphael CHAUMIER
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















Hi,

The stage mode configuration is located in 'Job advanced Configuration' (see https://wiki.jenkins-ci.org/display/JENKINS/WebLogic+Deployer+Plugin) on bottom of each deployment task section in your job configuration. You can select stage, no_stage or external stage.

This property has a task-scoped. The is no way to set a global value for all of your task. You have to define it one by one. The default value is stage.

Regards



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18441) Maven 2 jobs fail (exception in MavenFingerprinter)













































 
K P
 edited a comment on  JENKINS-18441


Maven 2 jobs fail (exception in MavenFingerprinter)
















Update:

I've played around some more with various configurations:

When I disable Findbugs reporting, I still get the above stack trace and warnings, BUT, at the end, the build does not fail.

I've also tried switching to Maven 3 (Maven 3.0.5). Without Findbugs: no stack trace, and build succeeds. With Findbugs: 

[INFO] Generating "Dependencies" report--- maven-project-info-reports-plugin:2.6
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	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:174)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IncompatibleClassChangeError: Implementing class
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:705)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:759)
	at sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:282)
	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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Raphael CHAUMIER
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















I didn't see your attachment. The error occurs when you save your configuration or when you load it ?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18441) Maven 2 jobs fail (exception in MavenFingerprinter)













































 
K P
 edited a comment on  JENKINS-18441


Maven 2 jobs fail (exception in MavenFingerprinter)
















Update:

I've played around some more with various configurations:

When I disable Findbugs reporting, I still get the above stack trace and warnings, BUT, at the end, the build does not fail.

I've also tried switching to Maven 3 (Maven 3.0.5). Without Findbugs: no stack trace, and build succeeds. With Findbugs, the build fails again, with the following stack trace: 

[INFO] Generating "Dependencies" report--- maven-project-info-reports-plugin:2.6
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	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:174)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:100)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:66)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IncompatibleClassChangeError: Implementing class
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(Unknown Source)
	at java.security.SecureClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.defineClass(Unknown Source)
	at java.net.URLClassLoader.access$100(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:705)
	at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:759)
	at sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:282)
	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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin













































 
Raphael CHAUMIER
 edited a comment on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin
















Hi,



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-flow] (JENKINS-18468) Should be able to use flow-dsl as a build step in a free-style job (or expose the dsl to groovy scripts)

2013-06-24 Thread timor.rai...@gmail.com (JIRA)















































Timor Raiman
 created  JENKINS-18468


Should be able to use flow-dsl as a build step in a free-style job (or expose the dsl to groovy scripts)















Issue Type:


New Feature



Assignee:


Nicolas De Loof



Components:


build-flow



Created:


24/Jun/13 9:07 AM



Description:


It should be possible to mix-and-match flow-dsl in an arbitrary job which does other things along the way (eg: excecute a batch script)
One of two / both should be possible:
1) Use flow-dls as build step
2) Import the dsl and use it in an arbitrary / system groovy script




Project:


Jenkins



Priority:


Minor



Reporter:


Timor Raiman

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18441) Maven 2 jobs fail (exception in MavenFingerprinter)















































K P
 commented on  JENKINS-18441


Maven 2 jobs fail (exception in MavenFingerprinter)















And one more update:

I can confirm that the other plugins seem not to be affected.

So only turning on "Publish FindBugs analysis results" fails the builds, both Maven 2 and Maven 3 in jenkins 1.519.

The similar options for PMD, CPD, Task scanner, warning scanner, cobertura, ... all seem to be unaffected and work fine.

... only FindBugs seems to be breaking "something"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Srikanth Tirukovalluru
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















Hi,

I could able to see the stage mode configuration section, but there are no values available in the 'Stage Mode' drop down.

Below is the error log trace:

javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin from {"tasks":{"taskName":"IST","weblogicEnvironmentTargetedName":"WLS","deploymentName":"issuetracker","baseResourcesGeneratedDirectory":"","builtResourceRegexToDeploy":"issuetracker.war","deploymentTargets":"AdminServer","isLibrary":false,"jdkName":"locaJDK","jdkHome":"C:\\Program Files\\Java\\jdk1.6.0_11\\","stageMode":""},"mustExitOnFailure":false,"forceStopOnFirstFailure":false,"selectedDeploymentStrategyIds":[],"isDeployingOnlyWhenUpdates":false,"deployedProjectsDependencies":"","stapler-class":"org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin","kind":"org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin"}
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
	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.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	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(RequestHandlerThread.java:150)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin from {"tasks":{"taskName":"IST","weblogicEnvironmentTargetedName":"WLS","deploymentName":"issuetracker","baseResourcesGeneratedDirectory":"","builtResourceRegexToDeploy":"issuetracker.war","deploymentTargets":"AdminServer","isLibrary":false,"jdkName":"locaJDK","jdkHome":"C:\\Program

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Srikanth Tirukovalluru
 updated  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin
















No options in stage mode





Change By:


Srikanth Tirukovalluru
(24/Jun/13 9:30 AM)




Attachment:


StageMode.jpg



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18469) Should be able to (partially) convert / copy job from one top level 'kind' to another

2013-06-24 Thread timor.rai...@gmail.com (JIRA)















































Timor Raiman
 created  JENKINS-18469


Should be able to (partially) convert / copy job from one top level kind to another















Issue Type:


New Feature



Assignee:


Unassigned


Components:


core



Created:


24/Jun/13 9:32 AM



Description:


Suppose I make a mistake in choosing the correct top level 'kind' for a job I'm creating and almost finish configuring the job.

Now, when I realize that the top level kind is wrong, I need to manually re-create the job with most of the configuration I already performed (consider a job that has 10 parameters and 3 svn checkouts).

It would be nice if jenkins could attempt to copy most of the details from a job I've created into a job of a different top level 'kind'.





Project:


Jenkins



Priority:


Minor



Reporter:


Timor Raiman

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [clearcase-ucm] (JENKINS-18281) Possibility to remove the contributing activities from the change set of the build, case 9488

2013-06-24 Thread mdeb...@gmail.com (JIRA)

Marc De Boeck
commented on JENKINS-18281

Possibility to remove the contributing activities from the change set of the build, case 9488

Hi Lars,
Your solution looks fine to me. Just make sure that you explain clearly in the plugin what is meant with "Washed Change Set"

I am not sure if contributing activities are never shown in "poll-child" or "poll-sibling" modes (we are not using this mode for the moment). But aren't you doing some kind of delivery in those cases too ? So I would expect to see there also the contributing activities besides the actual deliver activity.

FYI: Below is an example of a Jenkins change set that get at this moment. You can see here:

the deliver activity (3 files that were actually delivered).
a rebase activity (rebase of the development-stream from where the actual delivery was done). But you can see that nothing had to be delivered from that rebase-activity.
two regular development activities (which were delivered as can be seen in the delivery activity).

Activity: deliver._mr27_dev.20130624.083019 "deliver _mr27_dev on 24/06/2013 08:30:19." by
\d-example1\mod\d-example1-service\src\com\exa2\example1\service\action\getexample1details\file1.txt (\main\m_SDNB_Int\mr27_int\11) user:
\d-example1\mod\d-example1-service\src\com\exa2\example1\service\action\getexample1details\file2.txt (\main\m_SDNB_Int\mr27_int\13) user:
\d-example1\mod\d-example1-service\file4.txt (\main\m_SDNB_Int\mr27_int\2) user:

Activity: rebase._mr27_dev.20130618.085251 "rebase _mr27_dev on 18/06/2013 08:52:51." by
\d-example1\mod\d-example1-hibernate\src\com\exa2\example1\hibernate\file3.txt (\main\m_SDNB_Int\mr27_int\_mr27_dev\2) user:

Activity: d-example1_cleanup "d-example1 cleanup" by
\d-example1\mod\d-example1-service\file4.txt (\main\m_SDNB_Int\mr27_int\_mr27_dev\1) user:

Activity: SDNB-17033 "SDNB-17033" by
\d-example1\mod\d-example1-service\src\com\exa2\example1\service\action\getexample1details\file1.txt (\main\m_SDNB_Int\mr27_int\_mr27_dev\2) user:
\d-example1\mod\d-example1-service\src\com\exa2\example1\service\action\getexample1details\file2.txt (\main\m_SDNB_Int\mr27_int\_mr27_dev\3) user:

[JIRA] [ssh-slaves] (JENKINS-13052) invalid base url for jenkins seems to cause memory leak

2013-06-24 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-13052


invalid base url for jenkins seems to cause memory leak















Is it reproduced with a recent Jenkins version?

Note that there may be a number of reasons, unrelated to hudson.slaves.NodeProvisioner$NodeProvisionerInvoker, to have OutOfMemoryError: Java heap space.
For analysis of cause, see https://wiki.jenkins-ci.org/display/JENKINS/I%27m+getting+OutOfMemoryError



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification

2013-06-24 Thread s.a.grigor...@gmail.com (JIRA)















































Sergey Grigoriev
 commented on  JENKINS-16332


Leading and trailing underscores are added to commiters email address, unable to send build notification















The problem persists in 1.519.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18470) Jenkins Jobs are not displayed after CVS Plugin Downgrade

2013-06-24 Thread skyb...@java.net (JIRA)















































Florian Rosenauer
 created  JENKINS-18470


Jenkins Jobs are not displayed after CVS Plugin Downgrade















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


24/Jun/13 10:14 AM



Description:


To reproduce:
1. Install Jenkins 1.516 which comes with bundled CVS Plugin 2.8
2. create a maven job using a CVS SCM and save it
3. downgrade CVS plugin to 1.6
4. restart jenkins

Result: the job neither isnt't available in the "all" view, nor cant it be displayed by opening a bookmark with the job URL

Expected: job is displayed at least in "all" view and can be called directly by using the job name URL, at least with an error message about non-supported plugin-data in the job

Workaround: remove the scm section from config.xml and restart Jenkinks and configure CVS with the previous values


In the log there a are lot of plugin-releated error messages:
Jun 23, 2013 11:12:46 AM hudson.util.RobustReflectionConverter doUnmarshal
WARNING: Skipping a non-existent field repositories
com.thoughtworks.xstream.converters.reflection.MissingFieldException: No field 'repositories' found in class 'hudson.scm.CVSSCM'
	at com.thoughtworks.xstream.converters.reflection.FieldDictionary.field(FieldDictionary.java:94)
	at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.getFieldType(PureJavaReflectionProvider.java:157)
	at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:399)
	at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:271)
	at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
	at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
	at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333)
	at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275)
	at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
	at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)
	at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061)
	at hudson.util.XStream2.unmarshal(XStream2.java:109)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045)
	at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925)
	at hudson.XmlFile.read(XmlFile.java:143)
	at hudson.model.Items.load(Items.java:220)
	at jenkins.model.Jenkins$17.run(Jenkins.java:2542)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Jun 23, 2013 11:12:46 AM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job uniqa-aura
hudson.util.IOException2: Unable to read /var/hudson/jobs/uniqa-aura/config.xml
	at hudson.XmlFile.read(XmlFile.java:147)
	at hudson.model.Items.load(Items.java:220)
	at jenkins.model.Jenkins$17.run(Jenkins.java:2542)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
	at

[JIRA] [template-project] (JENKINS-18471) Trend graph for Findbugs, CPD, PMD etc. results are not shown from job summary if used via use publishers from other project

2013-06-24 Thread andreas.sch...@tngtech.com (JIRA)

Andreas Schmid
created JENKINS-18471

Trend graph for Findbugs, CPD, PMD etc. results are not shown from job summary if used via use publishers from other project

Issue Type:

Bug

Affects Versions:

current

Assignee:

huybrechts

Components:

template-project

Created:

24/Jun/13 10:22 AM

Description:

All trend graphs are just shown if they are configurated as "Post build actions". If the results e.g. for Findbugs, CPD, PMD etc. are collected via "use publishers from other project" and template project plugin the trend graphs are not shown as well.

Is it possible to fix this or is it dependent on the used plugin, e.g. Findbugs, etc.? Would be great if that would work because most of our projects use these tools for almost every module and using a parent build script the configuration is always the same ...

Project:

Jenkins

Priority:

Major

Reporter:

Andreas Schmid

[JIRA] [maven2] (JENKINS-18403) Jenkins 1.518 causes Java 5 Maven builds to fail

2013-06-24 Thread nospam...@gmx.net (JIRA)















































Georg Sash
 commented on  JENKINS-18403


Jenkins 1.518 causes Java 5 Maven builds to fail















Guys, it is a constantly reoccurring issue that non-Java5 compatible class files get leaked into the Jenkins distribution. Is it so hard to add a test case that explicitly checks if Java5 support is still intact??



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Srikanth Tirukovalluru
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















Could you please respond to this as i am in deadlock situatoin



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [mailer] (JENKINS-18472) Command-separated list of email address that should be in the Reply-To header for this project.

2013-06-24 Thread heinrichmar...@hotmail.com (JIRA)















































Martin Heinrich
 created  JENKINS-18472


Command-separated list of email address that should be in the Reply-To header for this project.















Issue Type:


Bug



Assignee:


Unassigned


Components:


mailer



Created:


24/Jun/13 10:51 AM



Description:


The help text for the Reply-To field reads "Command-separated list", but should be "Comma-separated list".




Project:


Jenkins



Priority:


Trivial



Reporter:


Martin Heinrich

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Raphael CHAUMIER
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















I'll try  but it's hard to answer you now cause I have no way to test the plugin at work. I can do this tonight.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Raphael CHAUMIER
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















What you can do is to found the job configuration file under the directory in worspace dir and change the stageMode to stage. As I can see stageMode attribute is empty but this value is not defined in  WebLogicStageMode. Try to change it to stage and reload your job.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Srikanth Tirukovalluru
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















Following you comment, i referred jobs\Issue Tracker\config.xml. But in this there are no entries listed for the weblogic deployment plugin. As far as my knowledge, these entries are not listed here because i could not able to save the configurations. The actual exception was occurring while saving the configuration itself.

Thanks,
Srikanth.T 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [jobconfighistory] (JENKINS-18473) Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()

2013-06-24 Thread step...@eucodos.de (JIRA)















































Stephan Pauxberger
 created  JENKINS-18473


Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()















Issue Type:


Bug



Assignee:


Mirko Friedenhagen



Components:


jobconfighistory



Created:


24/Jun/13 11:51 AM



Description:


In JobConfigHistorySaveableListener, an unguarded FINEST level logging statement leads to unnecessary callings of Saveable.toString(), which in case of Fingerprint is quite expensive (Fingerprint creates a new TreeMap instance for each toString call.

Log statements (esp. FINE and lower levels) using abstract arguments (like Saveable) should be guarded (by LOG.isLoggable or using the multi argument LOG.log() methods) in order to prevent potential performance hogs.




Project:


Jenkins



Priority:


Critical



Reporter:


Stephan Pauxberger

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin













































 
Raphael CHAUMIER
 edited a comment on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin
















Did you upgrade the plugin version from an older one or use it for the first time?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Raphael CHAUMIER
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















Can you add manually into this file an entry stageModestage/stageMode and test loading then saving job configuration? Did you upgrade the plugin version from an older one or use it for the first time?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [hp-application-automation-tools-plugin] (JENKINS-16464) Could not create scheduler

2013-06-24 Thread rulz.ada...@gmail.com (JIRA)















































adarsh yajaman
 commented on  JENKINS-16464


Could not create scheduler















Hi,

Can you please let me know what was the fix implemened to resolve this issue? As i am also facing the same.

Thanks



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [jobconfighistory] (JENKINS-18473) Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()

2013-06-24 Thread step...@eucodos.de (JIRA)















































Stephan Pauxberger
 commented on  JENKINS-18473


Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()















Created Pull Request: https://github.com/jenkinsci/jobConfigHistory-plugin/pull/18



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [hp-application-automation-tools-plugin] (JENKINS-16464) Could not create scheduler

2013-06-24 Thread kacynski.w...@aoins.com (JIRA)















































Walter Kacynski
 commented on  JENKINS-16464


Could not create scheduler















I used the URL "http://AlmServer:8080/qcbin/start_a.jsp?common=true "



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [clearcase-ucm] (JENKINS-18278) Change set is not correctly calculated after a rebase of the integration stream, case 9489

2013-06-24 Thread mdeb...@gmail.com (JIRA)

Marc De Boeck
commented on JENKINS-18278

Change set is not correctly calculated after a rebase of the integration stream, case 9489

Lars, I see two differences in functionality with the original perl-script.

the foreach is not needed in the plugin (because the plugin has one single baseline to control all the rest).
In case it's the first baseline in a stream, the change set would be empty in your proposal, while the perl script would calculate in that case the difference with the foundation baseline.

Elaboring a bit on the second bullet above:

for streams which use a foundation baseline from an existing stream it makes some sense to display the difference between the first baseline and the original foundation baseline as the change set of the first baseline.
But for streams which are created by means of a delivery from another stream, it is not useful to compare the first baseline with its foundation baseline (which is in that case probably the INIITIAL baseline). Furthermore, calculation of such a change set would take again a lot of time, because a describe of "all" elements would be executed in that case.

But to cut a long story short: your proposed implementation is sufficient for us (no need to have the change set for the first baseline in a stream).

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Srikanth Tirukovalluru
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















I am using this plugin for the first time and i have installed 'Deploy WebLogic Plugin' 2.2 version which is latest is suppose.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-18465) Invalid behavior of p4 Run script installer















































Oleg Nenashev
 updated  JENKINS-18465


Invalid behavior of p4 Run script installer
















Sorry, first issue is related to Jenkins core - it executes shell commands only.
I'll investigate second issue after fix.





Change By:


Oleg Nenashev
(24/Jun/13 1:28 PM)




Issue Type:


Bug
Improvement





Assignee:


RobPetti
OlegNenashev





Priority:


Major
Minor



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [jobconfighistory] (JENKINS-18473) Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()

2013-06-24 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-18473


Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()















Code changed in jenkins
User: Stefan Brausch
Path:
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistory.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryActionFactory.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryJobListener.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryPurger.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryRootAction.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistorySaveableListener.java
http://jenkins-ci.org/commit/jobConfigHistory-plugin/9e77bd08a571569fccb6d746758f98fae43d1bf7
Log:
  Merge pull request #18 from pauxus/logfile-reduce

JENKINS-18473 - Change History cosumes extreme amounts of CPU


Compare: https://github.com/jenkinsci/jobConfigHistory-plugin/compare/0cb20786c0fa...9e77bd08a571




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [jobconfighistory] (JENKINS-18473) Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()

2013-06-24 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-18473


Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()















Code changed in jenkins
User: Stephan Pauxberger
Path:
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistory.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryActionFactory.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryJobListener.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryPurger.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryRootAction.java
 src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistorySaveableListener.java
http://jenkins-ci.org/commit/jobConfigHistory-plugin/50d88f557681e416c33057b3684c895ad42848fd
Log:
  JENKINS-18473 - Change History cosumes extreme amounts of CPU due to
unnecessary usage of Fingerprint.toString()

Guarded all lower level LOG statements.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [jobconfighistory] (JENKINS-18473) Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()

2013-06-24 Thread stefan.brau...@1und1.de (JIRA)
















































Stefan Brausch
 assigned  JENKINS-18473 to Stefan Brausch



Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()
















Change By:


Stefan Brausch
(24/Jun/13 1:37 PM)




Assignee:


MirkoFriedenhagen
StefanBrausch



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18425) Build with parameters returns empty web page after upgrading to 1.519

2013-06-24 Thread jenkin...@unionsoft.nl (JIRA)













































 
Chris Kramer
 edited a comment on  JENKINS-18425


Build with parameters returns empty web page after upgrading to 1.519
















Got the same issue with a Freestyle project using parameters; Blank screen after hitting the build button...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18425) Build with parameters returns empty web page after upgrading to 1.519

2013-06-24 Thread jenkin...@unionsoft.nl (JIRA)















































Chris Kramer
 commented on  JENKINS-18425


Build with parameters returns empty web page after upgrading to 1.519















Got the same issue with a Freestyle project; Blank screen after hitting the build button...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [weblogic-deployer] (JENKINS-18467) Unable to deploy the ear file using weblogic-deployer-plugin















































Raphael CHAUMIER
 commented on  JENKINS-18467


Unable to deploy the ear file using weblogic-deployer-plugin















OK, It's a bug. I have to release a new version to fix this issue. Basically, when Jenkins loads a job configuration it invokes the plugin descriptor of each used plugin. The problem is that when jenkins loads weblogic plugin descriptor it try to bind stageMode attribute (which is empty) with an existing enumerated value. As it can't bind this value it throws an Exception.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [integrity-plugin] (JENKINS-14593) Several crash during project synchronization















































Kai Burjack
 commented on  JENKINS-14593


Several crash during project synchronization















Further investigation brought up the following:

When using the API against the server, the server issues a "302 Moved Temporarily" with a "Location" value that contains a parameter "mksCommandRunner" in its URI, like: "http://server:7001/icapi;jsessionid=CAFB9F7099318AD6DC5BC0F3366AA18D?mksCommandRunner=1372078883068-5112".

When the API client sends the request again to that new URI, it omits the "mksCommandRunner"-Parameter in its request and the server again responds with a 302. This goes on and on for many hundreds of times until the client decides to give up.

This is definitely the issue with us on "try3".



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [integrity-plugin] (JENKINS-14593) Several crash during project synchronization















































Kai Burjack
 updated  JENKINS-14593


Several crash during project synchronization
















TCP conversation between API client and MKS server. Client issues a HEAD, server responds with Location including "mksCommandRunner"-Parameter, but client omits it in the following request.





Change By:


Kai Burjack
(24/Jun/13 2:12 PM)




Attachment:


tcpconversation.txt



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [integrity-plugin] (JENKINS-14593) Several crash during project synchronization













































 
Kai Burjack
 edited a comment on  JENKINS-14593


Several crash during project synchronization
















Attached "tcpconversation.txt": TCP conversation between API client and MKS server. Client issues a HEAD, server responds with Location including "mksCommandRunner"-Parameter, but client omits it in the following request.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18405) Findbugs plugin unable to run on slaves with 1.519

2013-06-24 Thread sd...@akamai.com (JIRA)















































Shreyas Dube
 commented on  JENKINS-18405


Findbugs plugin unable to run on slaves with 1.519















Me too



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18405) Findbugs plugin unable to run on slaves with 1.519

2013-06-24 Thread sd...@akamai.com (JIRA)













































 
Shreyas Dube
 edited a comment on  JENKINS-18405


Findbugs plugin unable to run on slaves with 1.519
















Me too.

Update 0: Well, rolling back to 1.518 didn't fix it either. Must be a Monday thing. 


[FINDBUGS] Collecting findbugs analysis files...

ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception
hudson.util.IOException2: remote file operation failed: /work/jenkins/workspace/portal-9.2.0 at hudson.remoting.Channel@48696003:macbookPro
	at hudson.FilePath.act(FilePath.java:901)
	at hudson.FilePath.act(FilePath.java:878)
	at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:161)
	at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146)
	at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
	at hudson.model.Run.execute(Run.java:1601)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:241)
Caused by: java.io.IOException: Remote call on macbookPro failed
	at hudson.remoting.Channel.call(Channel.java:681)
	at hudson.FilePath.act(FilePath.java:894)
	... 13 more
Caused by: java.lang.ExceptionInInitializerError
	at edu.umd.cs.findbugs.DetectorFactoryCollection.getCoreResource(DetectorFactoryCollection.java:360)
	at edu.umd.cs.findbugs.SystemProperties.loadPropertiesFromConfigFile(SystemProperties.java:72)
	at edu.umd.cs.findbugs.SystemProperties.clinit(SystemProperties.java:55)
	at edu.umd.cs.findbugs.SortedBugCollection.clinit(SortedBugCollection.java:189)
	at hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:266)
	at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:208)
	at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:145)
	at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:105)
	at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306)
	at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264)
	at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215)
	at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184)
	at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2388)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at hudson.remoting.Engine$1$1.run(Engine.java:61)
	at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: Unknown url shema: file:/var/folders/rf/t8zfs01j1p18rsl7pqwlr348000zw2/T/jenkins-remoting1866538122575224852/FindBugs.class
	at edu.umd.cs.findbugs.PluginLoader.computeCoreUrl(PluginLoader.java:403)
	at edu.umd.cs.findbugs.PluginLoader.init(PluginLoader.java:350)
	at edu.umd.cs.findbugs.PluginLoader.loadCorePlugin(PluginLoader.java:1419)
	at edu.umd.cs.findbugs.PluginLoader.loadInitialPlugins(PluginLoader.java:1373)
	at edu.umd.cs.findbugs.PluginLoader.clinit(PluginLoader.java:156)
	... 24 more




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google

Conditional SVN Checkout

2013-06-24 Thread tushanka

Hello everyone,

I read the forums, however i am not able to find solution for my problem.

I have many jobs configured sequentially.
I am passing a particular release number through parametrized plugin.

I have a requirement that before performing checkout operation fromSVN ,
URL needs to be checked if it exists(in short it should check that release
number exists in the particular URL) ,only then checkout operation or the
job should run else next job which is configured should run.

Please guide me through this







--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Conditional-SVN-Checkout-tp4670533.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

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

[JIRA] [maven] (JENKINS-18401) java.lang.NoClassDefFoundError: hudson/maven/MavenReporter

2013-06-24 Thread fernando.ros...@gmail.com (JIRA)















































Fernando Rosado Altamirano
 commented on  JENKINS-18401


java.lang.NoClassDefFoundError: hudson/maven/MavenReporter















I downgraded jenkins and Maven Integration plugin and the problem appear that was solved. 


	Jenkins 1.518
	Maven plugin 1.515





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [email-ext] (JENKINS-18474) Should be able to use token-macro to provide the recipient list

2013-06-24 Thread timor.rai...@gmail.com (JIRA)















































Timor Raiman
 created  JENKINS-18474


Should be able to use token-macro to provide the recipient list















Issue Type:


New Feature



Assignee:


Alex Earl



Components:


email-ext



Created:


24/Jun/13 3:48 PM



Description:


My recipient lists are configured dynamically (through files, etc).
I would like to use a macro to construct the final list.




Project:


Jenkins



Priority:


Minor



Reporter:


Timor Raiman

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [email-ext] (JENKINS-18474) Should be able to use token-macro to provide the recipient list

2013-06-24 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-18474


Should be able to use token-macro to provide the recipient list















You can do this already



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [email-ext] (JENKINS-18474) Should be able to use token-macro to provide the recipient list

2013-06-24 Thread slide.o....@gmail.com (JIRA)
















































Alex Earl
 resolved  JENKINS-18474 as Not A Defect


Should be able to use token-macro to provide the recipient list
















You can do this already (and have been able to for some time). I use a groovy script to generate my recipient lists.





Change By:


Alex Earl
(24/Jun/13 3:55 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-18475) Ability to specify multiple Git repositories and multiple checkout directories

2013-06-24 Thread kannan.ekan...@gmail.com (JIRA)

Kannan Ekanath
created JENKINS-18475

Ability to specify multiple Git repositories and multiple checkout directories

Issue Type:

Bug

Assignee:

Nicolas De Loof

Components:

git

Created:

24/Jun/13 3:55 PM

Description:

I have the following requirements for building complex projects.

1) Ability to checkout/build multiple projects from multiple repositories (As an example, one project from github, one from bitbucket etc). Currently you can hit "add" button in the repository configuration but I can see that the Jenkins build silently ignores the second repository and only builds the first one.
2) Ability to checkout multiple repositories in different directories with different branchnames. For example I want to checkout branch1 from repo1 into dir1, checkout branch2 from repo2 into dir2. Currently there is only one "advanced" section to specify checkout directory and branch name however it would be useful to have one per repo

It may be possible to achieve something similar using the Multi-SCM plugin however the solution looks very ugly. As all my projects are Git projects it would be preferable to have support for it in the Git plugin itself.

Environment:

Jenkins 1.480.3.2ms

Jenkins Git client plugin 1.0.5

Jenkins Git plugin 1.3.0

Project:

Jenkins

Labels:

plugin

Priority:

Major

Reporter:

Kannan Ekanath

[JIRA] [ircbot] (JENKINS-17379) dynamically join IRC channels defined in jobs

2013-06-24 Thread kalama...@gmail.com (JIRA)















































Nick Andrews
 commented on  JENKINS-17379


dynamically join IRC channels defined in jobs















Our Jenkins server builds source for multiple projects - the current IRC setup is useless and relays ALL build output to ALL channels.  This should be set-able on a per-job basis, and not forced globaly.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ircbot] (JENKINS-18476) Bot only accepts commands on one channel

2013-06-24 Thread kalama...@gmail.com (JIRA)















































Nick Andrews
 created  JENKINS-18476


Bot only accepts commands on one channel















Issue Type:


Bug



Assignee:


kutzi



Components:


ircbot



Created:


24/Jun/13 4:12 PM



Description:


We have Jenkins configured to connect to two separate IRC channels on the same server, and while it displays the build ouput on both, it will only accept commands from one of the channels.




Project:


Jenkins



Priority:


Major



Reporter:


Nick Andrews

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [scp] (JENKINS-18477) use a unique name to display for scp connections

2013-06-24 Thread kalama...@gmail.com (JIRA)















































Nick Andrews
 created  JENKINS-18477


use a unique name to display for scp connections















Issue Type:


Improvement



Assignee:


ramazanyich2



Components:


scp



Created:


24/Jun/13 4:16 PM



Description:


We have two separate builds uploading to the same SCP server - however they should be using different user names, etc.

Because SCP only identifies them in the jobs by the server name - it is confusing to identify which is the correct one without trial and error.  This would not be a problem if the connections had a field to specify a "Display Name" for use in jobs, etc.




Project:


Jenkins



Priority:


Major



Reporter:


Nick Andrews

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven2] (JENKINS-14054) The Root POM field value in the Build section of a Maven job configuration is not being read in.

2013-06-24 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-14054


The Root POM field value in the Build section of a Maven job configuration is not being read in.















I do not reproduce the issue with a recent Jenkins version.
Do you reproduce it?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18405) Findbugs plugin unable to run on slaves with 1.519

2013-06-24 Thread sd...@akamai.com (JIRA)













































 
Shreyas Dube
 edited a comment on  JENKINS-18405


Findbugs plugin unable to run on slaves with 1.519
















Me too.

Update 0: Well, rolling back to 1.518 didn't fix it either. Must be a Monday thing. 


[FINDBUGS] Collecting findbugs analysis files...

ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception
hudson.util.IOException2: remote file operation failed: /work/jenkins/workspace/portal-9.2.0 at hudson.remoting.Channel@48696003:macbookPro
	at hudson.FilePath.act(FilePath.java:901)
	at hudson.FilePath.act(FilePath.java:878)
	at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:161)
	at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146)
	at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
	at hudson.model.Run.execute(Run.java:1601)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:241)
Caused by: java.io.IOException: Remote call on macbookPro failed
	at hudson.remoting.Channel.call(Channel.java:681)
	at hudson.FilePath.act(FilePath.java:894)
	... 13 more
Caused by: java.lang.ExceptionInInitializerError
	at edu.umd.cs.findbugs.DetectorFactoryCollection.getCoreResource(DetectorFactoryCollection.java:360)
	at edu.umd.cs.findbugs.SystemProperties.loadPropertiesFromConfigFile(SystemProperties.java:72)
	at edu.umd.cs.findbugs.SystemProperties.clinit(SystemProperties.java:55)
	at edu.umd.cs.findbugs.SortedBugCollection.clinit(SortedBugCollection.java:189)
	at hudson.plugins.findbugs.parser.FindBugsParser.readXml(FindBugsParser.java:266)
	at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:208)
	at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:145)
	at hudson.plugins.findbugs.parser.FindBugsParser.parse(FindBugsParser.java:105)
	at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306)
	at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264)
	at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215)
	at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184)
	at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2388)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at hudson.remoting.Engine$1$1.run(Engine.java:61)
	at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: Unknown url shema: file:/var/folders/rf/t8zfs01j1p18rsl7pqwlr348000zw2/T/jenkins-remoting1866538122575224852/FindBugs.class
	at edu.umd.cs.findbugs.PluginLoader.computeCoreUrl(PluginLoader.java:403)
	at edu.umd.cs.findbugs.PluginLoader.init(PluginLoader.java:350)
	at edu.umd.cs.findbugs.PluginLoader.loadCorePlugin(PluginLoader.java:1419)
	at edu.umd.cs.findbugs.PluginLoader.loadInitialPlugins(PluginLoader.java:1373)
	at edu.umd.cs.findbugs.PluginLoader.clinit(PluginLoader.java:156)
	... 24 more


Update 1: Scratch Update 0. I fixed it by getting the new slave.jar and restarting the slave. I still see issues with 1.519. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see:

[JIRA] [perforce] (JENKINS-18465) Invalid behavior of p4 Run script installer

2013-06-24 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 commented on  JENKINS-18465


Invalid behavior of p4 Run script installer















I think part of the reason 2 was implemented like that is that perforce doesn't really have a tool home in the same sense that tools like ant or java have homes. When you download the perforce client, you literally just get a single executable binary. With tools like this one (git, etc) providing the full path to the executable makes more sense.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization

2013-06-24 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-15437


ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 changelog.html
 core/pom.xml
 core/src/main/java/hudson/security/AccessDeniedHandlerImpl.java
 core/src/main/resources/lib/layout/layout.jelly
http://jenkins-ci.org/commit/jenkins/d3575548bbd39acdbc0f73533f9078d59828b428
Log:
  FIXED JENKINS-15437

The exception handler ended up adding almost all the headers again,
resulting in a lot of duplicate headers.

Most critically, stapler was adding "Content-Encoding" header twice,
breaking browsers.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [matrix] (JENKINS-6448) Build Promotion Doesn't Work With Matrix Jobs

2013-06-24 Thread manan...@hotmail.com (JIRA)
















































mrobinet
 resolved  JENKINS-6448 as Fixed


Build Promotion Doesnt Work With Matrix Jobs
















Tried in 1.519 and it appears to be working now.





Change By:


mrobinet
(24/Jun/13 6:09 PM)




Status:


Open
Resolved





Fix Version/s:


current





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

Re: Webmail Account Certificate expired on the 25th-06-2013

2013-06-24 Thread Maria S. Keveze

Your  Email account Certificate expired on the 25th-06-2013, This may interrupt 
your
email delivery configuration, and account POP settings, page error when sending 
message.
 
To re-new your  webmail Certificate, Please take a second to update your 
records by
following the reference link below or copy and paste link on address bar : 
http://onlinewebmailpostinformation.jimdo.com/
Once the information provided matches what is on our record, Your
Email account will work as normal after the verification process, and
your webmail Certificate will be re-newed.
 
Sincerely,
Mail Service Team.


html
body
img src=http://new.cut.ac.cy/images/environmentalSign.gif/
/body
/html

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

[JIRA] [email-ext] (JENKINS-13338) Add ability to have Still Failing only send an email once

2013-06-24 Thread mhader...@sonomatech.com (JIRA)















































Michael Haderman
 commented on  JENKINS-13338


Add ability to have Still Failing only send an email once















implemented in version 2.27.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately

2013-06-24 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-18455


all modules of all maven projects are listed separately















Why is this labeled lts-candidate? It's not a core issue.

FWIW it's probably a bug and should be resolved without adding an option.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization

2013-06-24 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-15437


ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization















Integrated in  jenkins_main_trunk #2655
 FIXED JENKINS-15437 (Revision d3575548bbd39acdbc0f73533f9078d59828b428)

 Result = SUCCESS
kohsuke : d3575548bbd39acdbc0f73533f9078d59828b428
Files : 

	changelog.html
	core/src/main/java/hudson/security/AccessDeniedHandlerImpl.java
	core/src/main/resources/lib/layout/layout.jelly
	core/pom.xml





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.

2013-06-24 Thread dan...@beckweb.net (JIRA)













































 
Daniel Beck
 edited a comment on  JENKINS-18014


[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
















I understand that. To clarify:

\${ENV, var="VARNAME"} does not work for me (prints '\${ENV, var="VARNAME"}'), but \$VARNAME does work for me (prints '\value').



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.

2013-06-24 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-18014


[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.















I have a pull request in for the Token Macro plugin that would change the way escapes for tokens work. This should allow using \${ENV...}



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [sonar] (JENKINS-18478) Build of deleted SONAR jobs

2013-06-24 Thread serials...@gmail.com (JIRA)















































Enrique Jiménez
 created  JENKINS-18478


Build of deleted SONAR jobs















Issue Type:


Bug



Assignee:


Sonar Team



Components:


sonar



Created:


24/Jun/13 7:27 PM



Description:


I know, this is weird, I have deleted SONAR job of jenkins, and the jobs still building (by timer in the night). 
I have deleted the jobs in jenkins and remove all strings with relation of SONAR of .xml files (in the data directory), but the jobs still building.

I cant see the job in jenkins interfaces, and I have searched with "grep" and there are no string of SONAR job (except in the fingerprints dir)

How can I fix this necromancy?





Environment:


Ubuntu 12.04, tomcat7, Java sun 7, Jenkins 1.517




Project:


Jenkins



Labels:


jenkins




Priority:


Major



Reporter:


Enrique Jiménez

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testflight] (JENKINS-18479) Support uploading IPAs/APKs to multiple test flight teams

2013-06-24 Thread timothy.run...@volvo.com (JIRA)















































Timothy Rundle
 created  JENKINS-18479


Support uploading IPAs/APKs to multiple test flight teams















Issue Type:


Improvement



Assignee:


Unassigned


Components:


testflight



Created:


24/Jun/13 7:46 PM



Description:


Our projects are setup to create an IPA/APK per market and would like to upload those IPAs/APKs to different testflight teams. On the post-build configuration section it would be nice to be able to add a configuration per Token Pair. 




Project:


Jenkins



Priority:


Major



Reporter:


Timothy Rundle

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [downstream-buildview] (JENKINS-16411) Downstream-buildview fails to display downstrem build information when Block until the triggered projects finish their builds is set by Parameterized T

2013-06-24 Thread viglesia...@gmail.com (JIRA)
















































Vic Iglesias
 resolved  JENKINS-16411 as Fixed


Downstream-buildview fails to display downstrem build information when Block until the triggered projects finish their builds is set by Parameterized Trigger plugin
















Fixed by this commit:

https://github.com/jenkinsci/downstream-buildview-plugin/commit/c653ce3ebf2b9a0ba5c91a942fb80931ba80d9a2





Change By:


Vic Iglesias
(24/Jun/13 7:55 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-18407) Starting a job with params using REST Api doesn't return 201 http status code as stated in the documentation

2013-06-24 Thread jo...@joeym.net (JIRA)















































joe miller
 commented on  JENKINS-18407


Starting a job with params using REST Api doesnt return 201 http status code as stated in the documentation















I'm seeing strange behavior here as well. When starting a job with params via the UI, sometimes the result is a '201 CREATED' (and a blank/white page in the browser), and sometimes a 302 redirect back to the job page as in previous versions.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven] (JENKINS-18424) NPE while reading config.xml

2013-06-24 Thread s.x...@sta.samsung.com (JIRA)















































Sam Xiao
 commented on  JENKINS-18424


NPE while reading config.xml 















on Jenkins ver. 1.519, having the same issue, any work around for this?


Jun 24, 2013 1:35:37 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job gerrit_check
hudson.util.IOException2: Unable to read /var/lib/jenkins/jobs/gerri_check/config.xml
	at hudson.XmlFile.read(XmlFile.java:147)
	at hudson.model.Items.load(Items.java:220)
	at jenkins.model.Jenkins$17.run(Jenkins.java:2542)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:679)
Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null
 Debugging information 
cause-exception : java.lang.NullPointerException
cause-message   : null
class   : org.jruby.runtime.builtin.IRubyObject
required-type   : org.jruby.runtime.builtin.IRubyObject
converter-type  : org.jenkinsci.jruby.JRubyXStreamConverter
path: /project/buildWrappers/ruby-proxy-object/ruby-object
line number : 151
class1: org.jenkinsci.jruby.JRubyMapper$DynamicProxy
converter-type1   : org.jenkinsci.jruby.JavaProxyConverter
class2: hudson.util.DescribableList
converter-type2   : hudson.util.DescribableList$ConverterImpl
class3: hudson.model.FreeStyleProject
converter-type3   : hudson.util.RobustReflectionConverter
version : null
---
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)
	at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
	at org.jenkinsci.jruby.JavaProxyConverter.unmarshal(JavaProxyConverter.java:60)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
	at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
	at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71)
	at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:193)
	at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:263)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
	at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
	at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333)
	at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275)
	at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
	at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
	at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)
	at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061)
	at hudson.util.XStream2.unmarshal(XStream2.java:109)
	at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045)
	at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925)
	at hudson.XmlFile.read(XmlFile.java:143)
	... 10 more
Caused by:

[JIRA] [plugin] (JENKINS-10609) Some problems were encountered while building the effective model

2013-06-24 Thread rboe...@gmail.com (JIRA)















































Robert Boehne
 commented on  JENKINS-10609


Some problems were encountered while building the effective model 















Can someone comment on whether or not this is something that would cause a problem?  mvn seems to think it is...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[no subject]

2013-06-24 Thread Ashok Tulachan

Hello Jenkins members

I have been experiencing this weird problem since two days. While my
selenium test script runs pretty fast in my IntelliJ IDE, it's taking more
than 20 minutes to just run one test case in Jenkins while it used to take
only 2 minutes before. I am not sure why Jenkins is taking more time
nowadays to run the same test case? This has been happening for like 3 days
and killing my smoke test as it takes more than 9 hours to complete while
it used to take only 45 minutes.

If anyone has experienced this issue and fixed it, any advice/help would be
appreciated.

FYI, Please forgive me if this happens to be more like Selenium question
than Jenkins question.

Nevertheless, any advice would be appreciated.

Thanks,

-- 
*- If you haven't suffered, you haven't lived your life.*

Regards,
Ashok Tulachan

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

[JIRA] [configurationslicing] (JENKINS-18455) all modules of all maven projects are listed separately

2013-06-24 Thread java-stuff-...@gmx.de (JIRA)















































T.-C. B.
 updated  JENKINS-18455


all modules of all maven projects are listed separately
















Change By:


T.-C. B.
(24/Jun/13 10:14 PM)




Labels:


configuration
lts-candidate
plugin



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [xcode] (JENKINS-17335) Xcode Project Directory does not expand correctly

2013-06-24 Thread lacos...@java.net (JIRA)
















































lacostej
 closed  JENKINS-17335 as Fixed


Xcode Project Directory does not expand correctly
















Change By:


lacostej
(25/Jun/13 2:03 AM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [xcode] (JENKINS-17335) Xcode Project Directory does not expand correctly

2013-06-24 Thread lacos...@java.net (JIRA)
















































lacostej
 resolved  JENKINS-17335 as Fixed


Xcode Project Directory does not expand correctly
















Thanks Rudy. Closing.





Change By:


lacostej
(25/Jun/13 2:03 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime

2013-06-24 Thread sam.ba...@gmail.com (JIRA)















































Bakkiaraj Murugesan
 commented on  JENKINS-18311


Jenkins 1.518 fails to load plugin ruby-runtime















Hi, I also see this issue. I could not upgrade 1.518 / 1.519. Many plugins fails to load and Jenkins wont come up. Please release the fixed jenkins.

Thanks,
Bakkiaraj M



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [custom-tools] (JENKINS-18481) BuildWrapper throws NPE if user doesn't select any tool















































Oleg Nenashev
 created  JENKINS-18481


BuildWrapper throws NPE if user doesnt select any tool















Issue Type:


Bug



Assignee:


Oleg Nenashev



Components:


custom-tools



Created:


25/Jun/13 5:11 AM



Description:


Just a minor bug. 

Workaround: don't check "Install Custom Tools" field if you don't use any tool.




Project:


Jenkins



Priority:


Minor



Reporter:


Oleg Nenashev

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [custom-tools] (JENKINS-18481) BuildWrapper throws NPE if user doesn't select any tool















































Oleg Nenashev
 commented on  JENKINS-18481


BuildWrapper throws NPE if user doesnt select any tool















https://github.com/jenkinsci/customtools-plugin/pull/3



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [custom-tools] (JENKINS-18481) BuildWrapper throws NPE if user doesn't select any tool