[JIRA] (JENKINS-13490) Passing multiline text parameter to ant broken (windows)
Martin Reck commented on JENKINS-13490 Passing multiline text parameter to ant broken (windows) Can we use the Ant commandline parameter -propertyfile? 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
[JIRA] (JENKINS-15971) java.lang.ClassNotFoundException: hudson.plugins.em ma.EmmaPublisher
Maruf Aytekin created JENKINS-15971 java.lang.ClassNotFoundException: hudson.plugins.em ma.EmmaPublisher Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: emma Created: 29/Nov/12 8:19 AM Description: Getting following error and emma coverage reports are not showing. WARNING: Failed to load hudson.plugins.emma.EmmaPublisher java.lang.InstantiationException: file:/weblogic/archiva/hudson/plugins/emma/WEB-INF/classes/META-INF/an notations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: hudson.plugins.em ma.EmmaPublisher at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:611) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:600) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:296) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) 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:585) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) 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:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassNotFoundException: hudson.plugins.emma.EmmaPublisher at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:934) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 26 more Environment: Jenkins ver. 1.492 Jenkins Emma plugin 1.29 Emma Line Coverage Column 0.0.4 Project: Jenkins Priority: Major Reporter: Maruf Aytekin 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
[JIRA] (JENKINS-15972) No display available in post build actions
Yves Langisch created JENKINS-15972 No display available in post build actions Issue Type: Bug Assignee: zregvart Components: xvfb Created: 29/Nov/12 8:22 AM Description: We need to have a display during the Sonar analysis which is a Post Build Action. Apparently the plugin shuts down the display already after the normal build part. So, the display is not available anymore during the Sonar Build. Project: Jenkins Priority: Major Reporter: Yves Langisch 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
[JIRA] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs
Frédéric Camblor commented on JENKINS-15969 Build Stats Plugin Returns so much data it hangs Hi Maxfield, As a workaround to delete your chart, you can send a POST request to http://jenkins:8080/plugin/global-build-stats/deleteConfiguration?buildStatId=qTJa$m7WnHjwPakLc7PLhaer$ze*zypA = It will remove your problematic chart Before doing this, could you try opening http://jenkins:8080/plugin/global-build-stats/showChart?buildStatId=qTJa$m7WnHjwPakLc7PLhaer$ze*zypA to see if the chart displays correctly or not ? The /plugin/global-build-stats/json should not take really long : it only displays chart configuration (presently, I have 13 charts, and it takes only size=1Kb content=8Kb) In your case, the content files seems very big (5,9Mb) : could you try to open it and see what there is inside 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
[JIRA] (JENKINS-14916) Stackoverflow in annonymous mode
Karl-Heinz Marbaise commented on JENKINS-14916 Stackoverflow in annonymous mode I have found out that by changing the permissions in Jenkins to allow READ-View Permission for anonymous it doesn't produce this failure which is currently a work a round for me. 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
[JIRA] (JENKINS-15973) Show head and tail for long console outputs
Radim Kubacki created JENKINS-15973 Show head and tail for long console outputs Issue Type: Improvement Affects Versions: current Assignee: jieryn Components: console-column Created: 29/Nov/12 9:34 AM Description: If there is a long output from a build job the output in console trims its beginning and shows the tail. That's great because frequently you can find failures there. OTOH the head of the log is missing and this can be useful too: in many cases there will be some diagnostic info or command line showing what exactly is executed that can serve as a hint to track down build failures. My suggestion is to show some short part from the beginning of file together with the end. Project: Jenkins Priority: Minor Reporter: Radim Kubacki 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
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Harro Schmidt commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 When cleaning the workspace of a project using Jenkins ver. 1.492-SNAPSHOT on Java 6 I get the following error: Nov 29, 2012 11:05:18 AM org.apache.catalina.core.ApplicationContext log SEVERE: Error while serving http://mycisserver/net/jenkins/view/N2/job/myclient/doWipeOutWorkspace 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.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 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 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at
[JIRA] (JENKINS-15951) unable to use clearcase view which is already present. instead it is deleting that view.
Vincent Latombe closed JENKINS-15951 as Wont Fix unable to use clearcase view which is already present. instead it is deleting that view. Using any Jenkins SCM Plugin implies that you let the SCM plugin control the workspace. If you want to control the view externally, don't use the SCM plugin. Change By: Vincent Latombe (29/Nov/12 10:11 AM) Status: Open Closed Resolution: WontFix 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
[JIRA] (JENKINS-15974) FATAL: Failed to link the library: interface hudson.util.jna.Kernel32
Jan Seidel created JENKINS-15974 FATAL: Failed to link the library: interface hudson.util.jna.Kernel32 Issue Type: Bug Affects Versions: current Assignee: vjuranek Attachments: system_log.txt Components: disk-usage Created: 29/Nov/12 10:19 AM Description: I am facing an issue since 1.490 which may be related to https://issues.jenkins-ci.org/browse/JENKINS-15466. These error occurs occassionally - 1-3 time in the night when the nightly builds stress the system for 6 hours. I have this issue seen by now only when a job is triggered by cron. I tried upgrading the plugins and Jenkins to various versions from 1.490 to current with no luck. Restarting Jenkins solves the issue on short term. 00:54:28 originally caused by: 00:54:28 Started by timer 00:54:28 EnvInject - Loading node environment variables. 00:54:28 Building remotely on B00013_2 in workspace y:\Jenkins_slave\workspace\NB_Uppsala 00:54:28 Cleaning local Directory . 00:54:28 FATAL: Failed to link the library: interface hudson.util.jna.Kernel32 00:54:28 java.lang.UnsupportedOperationException: Failed to link the library: interface hudson.util.jna.Kernel32 00:54:28 at hudson.util.jna.InitializationErrorInvocationHandler.invoke(InitializationErrorInvocationHandler.java:28) 00:54:28 at $Proxy7.GetFileAttributesW(Unknown Source) 00:54:28 at hudson.util.jna.Kernel32Utils.getWin32FileAttributes(Kernel32Utils.java:76) 00:54:28 at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:80) 00:54:28 at hudson.Util.isSymlink(Util.java:322) 00:54:28 at hudson.Util.deleteRecursive(Util.java:283) 00:54:28 at hudson.Util.deleteContentsRecursive(Util.java:204) 00:54:28 at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) 00:54:28 at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144) 00:54:28 at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:799) 00:54:28 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:780) 00:54:28 at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:763) 00:54:28 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309) 00:54:28 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 00:54:28 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 00:54:28 at hudson.remoting.Request$2.run(Request.java:326) 00:54:28 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 00:54:28 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 00:54:28 at java.util.concurrent.FutureTask.run(Unknown Source) 00:54:28 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) 00:54:28 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 00:54:28 at java.lang.Thread.run(Unknown Source) 00:54:28 Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native 00:54:28 at hudson.util.jna.Kernel32Utils.load(Kernel32Utils.java:85) 00:54:28 at hudson.util.jna.Kernel32.clinit(Kernel32.java:37) 00:54:28 at hudson.util.jna.Kernel32Utils.getWin32FileAttributes(Kernel32Utils.java:76) 00:54:28 at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:80) 00:54:28 at hudson.Util.isSymlink(Util.java:322) 00:54:28 at hudson.plugins.disk_usage.DiskUsageThread$DiskUsageCallable.getFileSize(DiskUsageThread.java:168) 00:54:28 at hudson.plugins.disk_usage.DiskUsageThread$DiskUsageCallable.call(DiskUsageThread.java:162) 00:54:28 at hudson.plugins.disk_usage.DiskUsageThread$DiskUsageCallable.call(DiskUsageThread.java:149) 00:54:28 ... 9 more It seems mainly to affect one machine with several slaves on it but that is no unique setup in our cluster. The system logs tell something about issue with determining the disk space. I have been checking the machine. Itself is in a healthy state with loads of available disk space. Environment:
[JIRA] (JENKINS-15975) Allow Scriptler to be used in Conditional BuildStep plugin
Markus Hoofe created JENKINS-15975 Allow Scriptler to be used in Conditional BuildStep plugin Issue Type: Improvement Assignee: domi Components: scriptler Created: 29/Nov/12 10:40 AM Description: When using the conditional buildstep plugin it is not possible to select Scriptler as builder. This seems to be related to JENKINS-15445: Conditional BuildStep only checks for builders with the @DataBoundConstructor annotation which is missing in the ScriptlerBuilder constructor. I already tried adding the annotation, so Scriptler becomes selectable. I can also set the groovy script to execute and the parameters, but: neither the "scriptId" nor the "parameters" are stored in the project! Funny though, the "propagateParams" flag is stored. Using Scriptler as builder by it's own did work ok, by the way. I haven't done any further tests with the annotation and i actually don't know what "bad" influence it could have. And maybe the "unsaved" scriptId and parameters are related to some other bug. Project: Jenkins Priority: Major Reporter: Markus Hoofe 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
[JIRA] (JENKINS-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild
Murray Cumming created JENKINS-15977 java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 29/Nov/12 11:06 AM Description: I'm using jenkins 1.466.2 via the regular Ubuntu packages on Ubuntu Quantla (12.10) with the copyArtifact plugin (version 1.25) The console output for the build of one of my Jenkins projects consistently shows this: Started by user Murray Cumming Building in workspace /var/lib/jenkins/workspace/maliit-plugins Checkout:maliit-plugins / /var/lib/jenkins/workspace/maliit-plugins - hudson.remoting.LocalChannel@35e47b48 Using strategy: Default Last Built Revision: Revision 1004cc39badd17308a1fabfe0b72d1e762572b4b (origin/master) Fetching changes from 1 remote Git repository Fetching upstream changes from git://gitorious.org/maliit/maliit-plugins.git Commencing build of Revision 1004cc39badd17308a1fabfe0b72d1e762572b4b (origin/master) Checking out Revision 1004cc39badd17308a1fabfe0b72d1e762572b4b (origin/master) FATAL: hudson/maven/MavenModuleSetBuild java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:198) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.lang.ClassNotFoundException: hudson.maven.MavenModuleSetBuild at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) ... 10 more Project: Jenkins Priority: Major Reporter: Murray Cumming 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
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
Tomasz Zieleniewski commented on JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException Hi, I encounter the same issue. Jenkins ver. 1.492. 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
[JIRA] (JENKINS-15978) NPE on job-import plugin: impossible to import
Vassilena Treneva created JENKINS-15978 NPE on job-import plugin: impossible to import Issue Type: Bug Assignee: jieryn Components: job-import Created: 29/Nov/12 1:02 PM Description: When I selected the job I wanted to import I got: Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:175) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) 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:47) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) 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
[JIRA] (JENKINS-15978) NPE on job-import plugin: impossible to import
Vassilena Treneva updated JENKINS-15978 NPE on job-import plugin: impossible to import Change By: Vassilena Treneva (29/Nov/12 1:05 PM) Attachment: o.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
[JIRA] (JENKINS-15501) Can't do Rebuild Action if Use the Validating String Parameter Plugin(2.2)
cjo9900 commented on JENKINS-15501 Cant do Rebuild Action if Use the Validating String Parameter Plugin(2.2) I think to make this rebuild action a bit more extend-able it should expose a interface than can be implemented in other parameter plugins. This would then allow code reuse of the original process for the parameter and always have the same implementation. This would mean that the rebuild plugin does not have to know about all the different parameter types. 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
[JIRA] (JENKINS-13852) Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter
cjo9900 assigned JENKINS-13852 to cjo9900 Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter Change By: cjo9900 (29/Nov/12 1:25 PM) Assignee: huybrechts cjo9900 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
[JIRA] (JENKINS-13852) Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter
cjo9900 commented on JENKINS-13852 Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter Pull request done, https://github.com/jenkinsci/parameterized-trigger-plugin/pull/30 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
[JIRA] (JENKINS-13852) Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter
cjo9900 started work on JENKINS-13852 Allow speciying Git SHA1 commit id for next build(s) as Predefined parameter Change By: cjo9900 (29/Nov/12 1:24 PM) Status: Open InProgress 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
[JIRA] (JENKINS-15979) forgets builds, workspace of renamed job
G. Ann Campbell created JENKINS-15979 forgets builds, workspace of renamed job Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: build-publisher Created: 29/Nov/12 2:25 PM Description: I renamed a job yesterday on 1.491 and this morning, Jenkins showed it as having no builds - even though I could see them on the file system. Immediately after the renaming, Jenkins seemed to have "lost sight" of the existing workspace. So I fired another build and all was good. But this morning, it had "forgotten" both that build and the workspace again. Restarting Jenkins seems to have fixed it. (Hope I picked the right component...) Project: Jenkins Priority: Minor Reporter: G. Ann Campbell 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
[JIRA] (JENKINS-15901) Run shell script/batch job after prqa report generation
Jason Masters commented on JENKINS-15901 Run shell script/batch job after prqa report generation Hi Frank, There is a general issue with the post build options in that you can't control the order they happen in. There is however a plugin called 'Flexible Publish Plugin' which allows you to run Post Build tasks in a particular order. I don't think you need to worry about temporary files - in a sense every file left on the Slave after a build is a temporary file and there are ways of managing the slaves. Please let me know if you have any more questions. Regards, Jason 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
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
SCM/JIRA link daemon resolved JENKINS-15940 as Fixed WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException Change By: SCM/JIRA link daemon (29/Nov/12 3:11 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
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
sogabe assigned JENKINS-15940 to sogabe WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException Change By: sogabe (29/Nov/12 3:11 PM) Assignee: olamy sogabe 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
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
SCM/JIRA link daemon commented on JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException Code changed in jenkins User: Seiji Sogabe Path: changelog.html core/src/main/java/hudson/tasks/Maven.java http://jenkins-ci.org/commit/jenkins/75bad0954f3b70c0fe8e75b6e676e7bac00ec009 Log: FIXED JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException 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
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
sogabe commented on JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException It will be fixed in 1.494. 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
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
sogabe edited a comment on JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException It will be fixed in 1.494 but I'm not sure that JENKINS-15964 will be 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
[JIRA] (JENKINS-15904) Perforce plugin issues wrong error message when it can't start cmd.exe to run p4.exe
Rob Petti commented on JENKINS-15904 Perforce plugin issues wrong error message when it cant start cmd.exe to run p4.exe Yes, but how do you know what the actual exception 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
[JIRA] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis created JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: promoted-builds Created: 29/Nov/12 3:28 PM Description: My builds are for windows projects, but this issue would be the case with any project I assume. I have a build that is using a label, "win", which both winbuila01 and winbuilda02 are labelled with. Sometimes, the build happens on winbuila01: Started by user Charles Mathis Building remotely on winbuila01 in workspace d:\jenkins-slave\workspace\Deployer Using remote perforce client: jenkins_deployer--667683261 ...successfully builds... Notifying upstream projects of job completion Finished: SUCCESS But the promotion happens on winbuilda02: Started by user chmathis Building remotely on winbuilda02 in workspace D:\jenkins-slave\workspace\Deployer Promoting Deployer #173 Deployer $ cmd /c call C:\Windows\TEMP\hudson791959618011257982.bat ...unsuccessfully promotes... Notifying upstream projects of job completion Finished: FAILURE I would expect one of two things: 1) It to run the promotion on winbuila01 since it built it on winbuilda01 or 2) Copy down the build artifacts to winbuilda02 so that it can run the promotion there Neither seem to happen. Am I missing something? Or is this a bug? - The obvious workaround is to set the build to specific box instead of a label so that the build and promotions jobs do not roam, but that defeats the purpose of using slaves. Environment: Master: Linux Slave [webdeva03] Windows Server 2008 Slave [winbuilda01] Windows Server 2008 Project: Jenkins Labels: plugin promoted-builds artifact Priority: Minor Reporter: Charles Mathis 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
[JIRA] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 3:29 PM) Description: Mybuildsareforwindowsprojects,butthisissuewouldbethecasewithanyprojectIassume.Ihaveabuildthatisusingalabel,win,whichbothwinbuila01andwinbuilda02arelabelledwith.Sometimes,thebuildhappensonwinbuila01: StartedbyuserCharlesMathisBuildingremotelyonwinbuila01inworkspaced:\jenkins-slave\workspace\DeployerUsingremoteperforceclient:jenkins_deployer--667683261[...successfullybuilds...]NotifyingupstreamprojectsofjobcompletionFinished:SUCCESSButthepromotionhappensonwinbuilda02:StartedbyuserchmathisBuildingremotelyonwinbuilda02inworkspaceD:\jenkins-slave\workspace\DeployerPromotingDeployer#173[Deployer]$cmd/ccallC:\Windows\TEMP\hudson791959618011257982.bat[...unsuccessfullypromotes...]NotifyingupstreamprojectsofjobcompletionFinished:FAILUREIwouldexpectoneoftwothings:1)Ittorunthepromotiononwinbuila01sinceitbuiltitonwinbuilda01or2)Copydownthebuildartifactstowinbuilda02sothatitcanrunthepromotionthereNeitherseemtohappen.AmImissingsomething?Oristhisabug?-Theobviousworkaroundistosetthebuildtospecificboxinsteadofalabelsothatthebuildandpromotionsjobsdonotroam,butthatdefeatsthepurposeofusingslaves.:( 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
[JIRA] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 3:30 PM) Environment: Master:LinuxSlave[ webdeva03 winbuilda01 ]WindowsServer2008Slave[ winbuilda01 winbuilda02 ]WindowsServer2008 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
[JIRA] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 3:36 PM) Description: Mybuildsareforwindowsprojects,butthisissuewouldbethecasewithanyprojectIassume.Ihaveabuildthatisusingalabel,win,whichboth winbuila01 winbuilda01 andwinbuilda02arelabelledwith.Sometimes,thebuildhappenson winbuila01 winbuilda01 :StartedbyuserCharlesMathisBuildingremotelyon winbuila01 winbuilda01 inworkspaced:\jenkins-slave\workspace\DeployerUsingremoteperforceclient:jenkins_deployer--667683261[...successfullybuilds...]NotifyingupstreamprojectsofjobcompletionFinished:SUCCESSButthepromotionhappensonwinbuilda02:StartedbyuserchmathisBuildingremotelyonwinbuilda02inworkspaceD:\jenkins-slave\workspace\DeployerPromotingDeployer#173[Deployer]$cmd/ccallC:\Windows\TEMP\hudson791959618011257982.bat[...unsuccessfullypromotes...]NotifyingupstreamprojectsofjobcompletionFinished:FAILUREIwouldexpectoneoftwothings:1)Ittorunthepromotionon winbuila01 winbuilda01 sinceitbuiltitonwinbuilda01or2)Copydownthebuildartifactstowinbuilda02sothatitcanrunthepromotionthereNeitherseemtohappen.AmImissingsomething?Oristhisabug?-Theobviousworkaroundistosetthebuildtospecificboxinsteadofalabelsothatthebuildandpromotionsjobsdonotroam,butthatdefeatsthepurposeofusingslaves.:( 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
[JIRA] (JENKINS-15964) All configuration screens are stuck LOADING
kurt stam commented on JENKINS-15964 All configuration screens are stuck LOADING Not that I'm aware of. Vote it up the issue so hopefully it will gain visibility. 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
[JIRA] (JENKINS-15964) All configuration screens are stuck LOADING
kurt stam edited a comment on JENKINS-15964 All configuration screens are stuck LOADING Not that I'm aware of. Vote up the issue so hopefully it will gain visibility. 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
[JIRA] (JENKINS-15960) Please enable Remote access API
Nilesh Dubey updated JENKINS-15960 Please enable Remote access API Change By: Nilesh Dubey (29/Nov/12 3:53 PM) Summary: Enable Pleaseenable RemoteaccessAPI Description: Can Please,can remoteaccessAPIbeenabledintheviolationsplugin? 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
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
dogfood commented on JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException Integrated in jenkins_main_trunk #2113 FIXED JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException (Revision 75bad0954f3b70c0fe8e75b6e676e7bac00ec009) Result = SUCCESS Seiji Sogabe : 75bad0954f3b70c0fe8e75b6e676e7bac00ec009 Files : changelog.html core/src/main/java/hudson/tasks/Maven.java 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Jon Radon commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine There's a workaround, but it doesn't appear to work in the latest version. 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Jon Radon edited a comment on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine There's a workaround, but it doesn't appear to work in the latest version. Adding my vote for this. 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
[JIRA] (JENKINS-15904) Perforce plugin issues wrong error message when exception occurs on remote end
Rob Petti commented on JENKINS-15904 Perforce plugin issues wrong error message when exception occurs on remote end Updating ticket summary, since this is a pretty general problem it seems. It's not so much that it's 'hiding' errors, as it can't send exceptions back from the remote slave agent using the current implementation. The only notion that the master has that something is wrong is the lack of data being returned. I'd like to know how you are able to view the actual exception. It may help us find a way to transfer that exception back to the master and report it correctly. 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
[JIRA] (JENKINS-14782) SCM polling cripples the entire application server
Rob Petti resolved JENKINS-14782 as Cannot Reproduce SCM polling cripples the entire application server Haven't heard from reporter in a while, so I'm going to assume that this has been resolved on their end. Change By: Rob Petti (29/Nov/12 4:20 PM) Status: Open Resolved Resolution: CannotReproduce 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
[JIRA] (JENKINS-15981) Display more appropriate error on connection issues caused by SystemRoot not being set
Rob Petti created JENKINS-15981 Display more appropriate error on connection issues caused by SystemRoot not being set Issue Type: Bug Assignee: Unassigned Components: perforce Created: 29/Nov/12 4:29 PM Description: If SystemRoot is not correctly set (either to C:\WINNT or C:\Windows) the p4 client can fail to connect to the perforce server. The error message currently thrown indicates a connection problem, rather than an environment problem, and is very misleading. Error thrown by the client is: Connect to server failed; check $P4PORT. TCP connect to 127.0.0.1:1666 failed. socket: 127.0.0.1:1666: WSAEPROVIDERFAILEDINIT Which is equally unhelpful. It should display something like: Error running perforce client executable. Is the SystemRoot environment variable and/or plugin option set correctly? Environment: Windows Project: Jenkins Priority: Minor Reporter: Rob Petti 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
[JIRA] (JENKINS-15982) NullPointerException in CloudBees License Manager
jeremi joslin created JENKINS-15982 NullPointerException in CloudBees License Manager Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 29/Nov/12 5:11 PM Description: With the plugin CloudBees License Manager enabled, I cannot access my jenkins server. I upgraded my jenkins install on ubuntu using packages but now I'm getting the following error : java.lang.NullPointerException at com.cloudbees.jenkins.plugins.license.BootHook.innerOnLoaded(BootHook.java:59) at com.cloudbees.jenkins.plugins.license.BootHook.onLoaded(BootHook.java:49) at jenkins.model.Jenkins.init(Jenkins.java:845) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:214) If I remove this plugin it works well, except that I cannot see some of my projects as they are in folders. Environment: Jenkins ver. 1.492 Project: Jenkins Priority: Blocker Reporter: jeremi joslin 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
[JIRA] (JENKINS-15983) Possibility to define a custom SCM tag in project config
Lucien Weller created JENKINS-15983 Possibility to define a custom SCM tag in project config Issue Type: Improvement Assignee: teilo Components: m2release Created: 29/Nov/12 5:22 PM Description: As we have the requirement to use some well defined tag names when building a release, we extended m2release plugin to be able to define a custom SCM tag template that will be expanded when performing a release build. Project: Jenkins Priority: Major Reporter: Lucien Weller 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
[JIRA] (JENKINS-15983) Possibility to define a custom SCM tag in project config
Lucien Weller started work on JENKINS-15983 Possibility to define a custom SCM tag in project config Change By: Lucien Weller (29/Nov/12 5:24 PM) Status: Open InProgress 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
[JIRA] (JENKINS-15983) Possibility to define a custom SCM tag in project config
Lucien Weller commented on JENKINS-15983 Possibility to define a custom SCM tag in project config pull request opened on GitHub 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
[JIRA] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (29/Nov/12 6:34 PM) Labels: artifactpluginpromoted-builds slave 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
[JIRA] (JENKINS-15984) ClearCase Changelog Timestamp order is not descending like clearcase reports
pixman20 created JENKINS-15984 ClearCase Changelog Timestamp order is not descending like clearcase reports Issue Type: Improvement Affects Versions: current Assignee: Vincent Latombe Components: clearcase Created: 29/Nov/12 6:36 PM Description: The changelog currently displays changes in the following format: USER on DD/MM/ HH:MM:SS Example: USER on 29/11/2012 12:58:28 ClearCase reports the time from lshistory in: MMDD.HHMMSS The change log should use ClearCase's convention of descending time from year down to seconds rather than displaying the time in a region specific method (US is typically MM/DD/). Using /MM/DD HH:MM:SS should be universal. At the very least the format could be made part of the configuration. Environment: Windows Server 20003 Project: Jenkins Labels: clearcase timestamp changelog Priority: Trivial Reporter: pixman20 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
[JIRA] (JENKINS-15984) ClearCase changelog timestamp should be descending (YYYY/MM/DD HH:MM:SS) or configurable: not DD/MM/YYY
pixman20 updated JENKINS-15984 ClearCase changelog timestamp should be descending (/MM/DD HH:MM:SS) or configurable: not DD/MM/YYY Change By: pixman20 (29/Nov/12 6:37 PM) Summary: ClearCase ChangelogTimestamporderisnot changelogtimestampshouldbe descending likeclearcasereports (/MM/DDHH:MM:SS)orconfigurable:notDD/MM/YYY 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
[JIRA] (JENKINS-15984) ClearCase changelog date should be descending or configurable: YYYY/MM/DD ... rather than DD/MM/YYYY
pixman20 updated JENKINS-15984 ClearCase changelog date should be descending or configurable: /MM/DD ... rather than DD/MM/ Change By: pixman20 (29/Nov/12 6:38 PM) Summary: ClearCasechangelog timestamp date shouldbedescending ( orconfigurable: /MM/DD HH:MM:SS)orconfigurable:not ...ratherthan DD/MM/ YYY 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
[JIRA] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs
Maxfield Stewart commented on JENKINS-15969 Build Stats Plugin Returns so much data it hangs Frederic, Thanks for the response. I haven't yet tried just going straight to each chart I have other than hitting the JSON api for each to get data, which works fine. I'll test the individual charts today and see what I can find. There are a few charts that I don't know the key for, I had just made them recently, I do not know how to get the chart ID's for them outside the UI, is there any way to do that? I'm also unclear on what you mean by a "content file". Is this something in the Jenkins folders I can look at on disk? If so where is it? Thanks for your help so far I appreciate it! I'll respond back with the results of my individual chart testing. 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
[JIRA] (JENKINS-15150) Content is returned for HEAD requests when using gzip
Steffen Pingel commented on JENKINS-15150 Content is returned for HEAD requests when using gzip Looks like this was also reported on JENKINS-13480. 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
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
kurt stam commented on JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException Hi Sogabe, is there a build I can grab to test if this fixes JENKINS-15964? 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
[JIRA] (JENKINS-6604) Possible race condition in RemoteClassLoader renders slave unusable
SCM/JIRA link daemon commented on JENKINS-6604 Possible race condition in RemoteClassLoader renders slave unusable Code changed in jenkins User: olivier lamy Path: pom.xml http://jenkins-ci.org/commit/jenkins/76e31a3a5c039e317a84b4c3331e15c284d44435 Log: use last remoting 2.19 fix for JENKINS-6604 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
[JIRA] (JENKINS-6604) Possible race condition in RemoteClassLoader renders slave unusable
SCM/JIRA link daemon commented on JENKINS-6604 Possible race condition in RemoteClassLoader renders slave unusable Code changed in jenkins User: olivier lamy Path: changelog.html http://jenkins-ci.org/commit/jenkins/b80789474cacc64be4954f0f4473759311e80580 Log: changelog entry for JENKINS-6604 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
[JIRA] (JENKINS-15985) Common TestNG report on Matrix configuration project
Martin Hereu created JENKINS-15985 Common TestNG report on Matrix configuration project Issue Type: Improvement Affects Versions: current Assignee: nalin_makar Components: testng Created: 29/Nov/12 8:04 PM Description: I have a configuration that runs a group of TestNG tests in different slaves (nodes) and each test execution provides a TestNG report with the results. It would be great if it is possible to collect these reports and show them in the master node (the main job where the matrix is configured) as a single report. Project: Jenkins Priority: Major Reporter: Martin Hereu 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
[JIRA] (JENKINS-15986) Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed
David Resnick created JENKINS-15986 Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed Issue Type: Bug Affects Versions: current Assignee: Tomas Westling Components: build-failure-analyzer Created: 29/Nov/12 8:49 PM Description: In a job configuration screen pushing Apply brings up an empty error window; pushing Save brings the below error 500 stack trace. I mentioned build 1.463 because this it is mentioned in the plugin wiki page, not because I validated that the problem doesn't exist on pre 1.463 versions. A possible workaround may be found in this comment: https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer?focusedCommentId=65668033#comment-65668033 Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) 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:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) 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:47) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at
[JIRA] (JENKINS-15987) Allow scan-build to use environment variables for Target and XCode project sub-path (or any other parameter)
Andy Johns created JENKINS-15987 Allow scan-build to use environment variables for Target and XCode project sub-path (or any other parameter) Issue Type: Improvement Assignee: Josh Kennedy Attachments: Screen Shot 2012-11-29 at 1.26.27 PM.png Components: clang-scanbuild Created: 29/Nov/12 9:27 PM Description: We use environment variables in our build setup to control which target and what path is built, unfortunately scan-build doesn't support variables. Would be great if it did. See attachment for example of how we'd like to configure it. Project: Jenkins Priority: Major Reporter: Andy Johns 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
[JIRA] (JENKINS-14987) server response HTML - Error 500
Joel Wheeler commented on JENKINS-14987 server response HTML - Error 500 In my last comment I realized that I posted some "good" json output, and not the garbled json output. Sorry about that. The issue has occurred numerous times, and it always appears to be when the build is ultimately triggered by other builds which are automatically rebuilt due to a code change in CVS. Manually executing the build corrects the api problem. 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
[JIRA] (JENKINS-15150) Content is returned for HEAD requests when using gzip
Michael Clarke closed JENKINS-15150 as Duplicate Content is returned for HEAD requests when using gzip Change By: Michael Clarke (29/Nov/12 9:45 PM) Status: Open Closed Assignee: MichaelClarke Resolution: Duplicate 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
[JIRA] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs
Frédéric Camblor
commented on JENKINS-15969
Build Stats Plugin Returns so much data it hangs
You can retrieve chart ids by sending a GET request to http://jenkins:8080/plugin/global-build-stats/api/json?depth=2
Here, you will gather something like this :
{
"buildStatConfigs":[ {
"averageBuildTimeShown":false,
"buildFilters": {
"abortedShown":true,
"failuresShown":true,
"jobFilter":"ALL",
"launcherFilter":"ALL",
"nodeFilter":"ALL",
"notBuildShown":false,
"successShown":true,
"unstablesShown":true
},
"buildStatHeight":600,
"buildStatTitle":"Distribution over time",
"buildStatWidth":800,
"buildStatusesShown":true,
"dimensionsShown":["BUILD_COUNTER","BUILD_TOTAL_DURATION"],
"historicLength":48,
"historicScale":"HOURLY",
"id":"HERE THE ID",
"totalBuildTimeShown":true,
"yAxisChartType":"COUNT"
} ]
}
When I talked about the "content file", It is the size displayed in the chrome dev tool network tab : in your screenshot, we can see the JSON file is 5,90Mb which is very big compared to my JSON file.
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
[JIRA] (JENKINS-15988) Downstream buildview plugin should save the status of the downstream builds to the xml file.
Grigoriy Milman created JENKINS-15988 Downstream buildview plugin should save the status of the downstream builds to the xml file. Issue Type: New Feature Assignee: shinodkm Components: downstream-buildview Created: 30/Nov/12 1:18 AM Description: Downstream buildview plugin should not only visualize the status all the downstream builds but also save it to the xml / text file and publish link to the file. This will allow comparison difference between builds of the complex projects; archiving build history etc. so that we can graphically see that everything for this build has been completed successfully. Project: Jenkins Priority: Major Reporter: Grigoriy Milman 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
[JIRA] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs
Maxfield Stewart commented on JENKINS-15969 Build Stats Plugin Returns so much data it hangs Ahh, thank you for the response, yes the content file was my major concern something was clearly wrong. Unfortunately we had to restart Jenkins today for other reasons and when the restart completed all my build stat configs were gone. Once I recreated them, everything is work exactly as I'd expect it to. For record please note that the URL gave me to get my chart names is the same URL that was generating the content file and just spewing huge amounts of data right down to the depth=2 so I wouldn't have been able to discover the chart configuration names that way. As it is, because the restart deleted all my configs and the problem as gone away, you can probably close this ticket. Thanks for the help however! 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
[JIRA] (JENKINS-15477) Loading All Build History Fails - error 500
Szilard P commented on JENKINS-15477 Loading All Build History Fails - error 500 I get the same error with a jenkins 1.486 installation. Here is the full stack trace: http://pastebin.com/i5rLj47e 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
[JIRA] (JENKINS-9650) plugin for global build stats just hangs after clicking on create new chart
Kamal Mettananda reopened JENKINS-9650 plugin for global build stats just hangs after clicking on create new chart Plugin is hanging when the charts are being generated. Jenkins version: 1.471 Browser: Firefox Chrome Global build stats plugin version: 1.3 There are two charts; one for monthly and one for weekly stats. I am in doubt whether a separate bug is required, but thought of reporting against this existing one. Change By: Kamal Mettananda (30/Nov/12 6:06 AM) Resolution: CannotReproduce Status: Resolved Reopened 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
[JIRA] (JENKINS-14046) git operations occasionally hang in Jenkins on Windows
Juraj Michalek commented on JENKINS-14046 git operations occasionally hang in Jenkins on Windows Solution suggested by VonC works for me (http://stackoverflow.com/questions/10732940/git-operations-occasionally-hang-in-jenkins-on-windows): Setting the Path to Git executable to C:\Program Files (x86)\Git\cmd\git.exe (i.e. cmd and not bin!) and 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
[JIRA] (JENKINS-14046) git operations occasionally hang in Jenkins on Windows
Juraj Michalek edited a comment on JENKINS-14046 git operations occasionally hang in Jenkins on Windows Solution suggested by VonC works for me (http://stackoverflow.com/questions/10732940/git-operations-occasionally-hang-in-jenkins-on-windows): Setting the Path to Git executable to C:\Program Files (x86)\Git\cmd\git.exe (i.e. cmd and not bin!) 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
