[JIRA] [coverity-plugin] (JENKINS-30886) BUG: Could not find Coverity Analysis home directory
Title: Message Title Bakkiaraj Murugesan commented on JENKINS-30886 Re: BUG: Could not find Coverity Analysis home directory Hi [Jeff Grimmett], Thanks for the workaround. We do have same situation like you, We don't build in master but we build on various slaves. My Jenkins master is Linux and we have both windows and linux slaves. In this case, How do I add empty directory and configure Coverity plugin (until this bug gets fixed)?. Just for my understanding, I do tried to debug the issue and I saw the plugin java code, it checks for the dir exists. How did you trace the issue and pointed out its looking the dir in Jenkins master (Though I configure the tool location in the particular build node). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [coverity-plugin] (JENKINS-30886) BUG: Could not find Coverity Analysis home directory
Title: Message Title Bakkiaraj Murugesan commented on JENKINS-30886 Re: BUG: Could not find Coverity Analysis home directory Hi, Nope. Our installation on WIndows 2008 did not contain spaces. Its installed in C:\Coverity\CoverityStaticAnalysis We get error, SEVERE: null 956 java.lang.Exception: Directory: C:\Coverity\CoverityStaticAnalysis doesn't exist. 957 at jenkins.plugins.coverity.CoverityUtils.checkDir(CoverityUtils.java:102) 958 at jenkins.plugins.coverity.CheckConfig.checkNode(CheckConfig.java:255) 959 at jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:87) 960 at hudson.Launcher.decorateFor(Launcher.java:695) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [coverity-plugin] (JENKINS-30886) BUG: Could not find Coverity Analysis home directory
Title: Message Title Bakkiaraj Murugesan commented on JENKINS-30886 Re: BUG: Could not find Coverity Analysis home directory Even in Windows also, we face the similar issue, IN the Node configuration, Under "Coverity Static Analysis" -> "Location" = C:\Coverity\CoverityStaticAnalysis Error in Jenkins log -- SEVERE: null 956 java.lang.Exception: Directory: C:\Coverity\CoverityStaticAnalysis doesn't exist. 957 at jenkins.plugins.coverity.CoverityUtils.checkDir(CoverityUtils.java:102) 958 at jenkins.plugins.coverity.CheckConfig.checkNode(CheckConfig.java:255) 959 at jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:87) 960 at hudson.Launcher.decorateFor(Launcher.java:695) 961 at hudson.model.Slave.createLauncher(Slave.java:375) 962 at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:564) 963 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) 964 at hudson.model.Run.execute(Run.java:1741) 965 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 966 at hudson.model.ResourceController.execute(ResourceController.java:98) 967 at hudson.model.Executor.run(Executor.java:408) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [coverity-plugin] (JENKINS-30886) BUG: Could not find Coverity Analysis home directory
Title: Message Title Bakkiaraj Murugesan updated an issue Jenkins / JENKINS-30886 BUG: Could not find Coverity Analysis home directory Change By: Bakkiaraj Murugesan Environment: Both Windows and Linux has this problem . Jenkins installation Mode: Manual InstallJenkins Version: 1.632 Coverity Plugin Version: 1.6.0 Windows OS (2003 EE) JVM: java version "1.7.0_21"Java(TM) SE Runtime Environment (build 1.7.0_21-b11)Java HotSpot(TM) Client VM (build 23.21-b01, mixed mode, sharing)Linux OS (Fedora 20) JVM:java version "1.7.0_79"OpenJDK Runtime Environment (fedora-2.5.5.0.fc20-x86_64 u79-b14)OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [coverity-plugin] (JENKINS-26736) [COMMAND LINE ERROR] Extra token error in the cov-commit-defects and cov-analyze
Bakkiaraj Murugesan created JENKINS-26736 [COMMAND LINE ERROR] Extra token error in the cov-commit-defects and cov-analyze Issue Type: Bug Assignee: Ken Dang Components: coverity-plugin Created: 02/Feb/15 8:52 AM Description: I have upgraded to Coverity plugin 1.5.0. After the upgrade coverity builds started failing. I have following extra options in the job config page, Additional cov-analyze-java arguments: --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa space_here Additional cov-commit-defects arguments: --description "Test SW Commit" --ticker-mode none Build failed with following build error, Coverity cmd so far is: /opt/cov-analysis-linux64-7.5.0/bin/cov-analyze, --dir, /home/JENKINS_HOME/coverity/temp-5110247036894018110.tmp, --cpp, --all, --ticker-mode, none, , --enable-constraint-fpp, , --enable-callgraph-metrics, --force, --hfa cov_infra_sw_Build $ /opt/cov-analysis-linux64-7.5.0/bin/cov-analyze --dir /home/JENKINS_HOME/coverity/temp-5110247036894018110.tmp --cpp --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa Coverity Static Analysis version 7.5.0 on Linux 3.17.7-200.fc20.x86_64 x86_64 Internal version numbers: b5b2c6e5a6 p-gilroy-push-19219.652 COMMAND LINE ERROR Extra token '' at the end of the command line. Please only specify one value for each option and ensure that all options are preceded with the '' or '-' characters. Specify --help for assistance. Coverity /opt/cov-analysis-linux64-7.5.0/bin/cov-analyze returned 2, aborting... $ /opt/cov-analysis-linux64-7.5.0/bin/cov-commit-defects --dir /home/JENKINS_HOME/coverity/temp-8006006841231009923.tmp --host test.dom.com --port 6060 --stream test_sw --user test --description "Test SW Commit" --ticker-mode none COMMAND LINE ERROR Extra token 'SW' at the end of the command line. Please only specify one value for each option and ensure that all options are preceded with the '' or '-' characters. Specify --help for assistance. Coverity cov-commit-defects returned 2, aborting... When I ran the coverity commands manually, its working fine. Looks like some problem in parsing the command line arguments. To solve the issue, I found the following work around, I have changed job config like, Additional cov-analyze-java arguments: --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa Additional cov-commit-defects arguments: --description "Test_SW_Commit" --ticker-mode none Now build is working fine. Environment: Jenkins 1.598, Manual installation, Linux Cent OS 6.x, Sun JVM 1.7.x Coverity Analysis linux64 7.5.0 Project: Jenkins Labels: plugin coverity Priority: Critical Reporter: Bakkiaraj Murugesan 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/d/optout.
[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Bakkiaraj Murugesan commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden Another workaround, Just go to fullscreen mode in your browser (F11), You can see the Save / Apply buttons. 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/d/optout.
[JIRA] [core] (JENKINS-26384) Jenkins ver. 1.596 - Save / Apply buttons are hidden
Bakkiaraj Murugesan created JENKINS-26384 Jenkins ver. 1.596 - Save / Apply buttons are hidden Issue Type: Bug Assignee: Unassigned Attachments: chrome_fullscreen.png, chrome_screenshot.png, screenshot1.png Components: core Created: 12/Jan/15 6:08 AM Description: I have upgraded to Jenkins ver. 1.596, which is latest and greatest. I observe that, When you change the job config and try to save, You won’t see Save / Apply button. (please see screenshot) The real problem is Save / Apply button is hidden below the Jenkins footer overlay, Even when you try to scroll bottom most you won’t see the buttons. Workaround: In browser, Go to full screen mode (f11), You will see the buttons to Save / Apply. Apparently, this bug looks like a HTML layout issue. I have tried in multiple browsers and see the same issue. Environment: Jenkins ver. 1.596, Manual installation, Cent OS 6x, Sun Java 1.7 Project: Jenkins Priority: Major Reporter: Bakkiaraj Murugesan 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/d/optout.
[JIRA] [log-parser] (JENKINS-20805) CR: Please provide information when Log Parser is running to parse console log
Bakkiaraj Murugesan created JENKINS-20805 CR: Please provide information when Log Parser is running to parse console log Issue Type: Bug Affects Versions: current Assignee: rgoren Components: log-parser Created: 28/Nov/13 10:40 AM Description: Hi, In the end of the build, While Log Parser is running to parse the console log, Please provide some information saying that log parser is running. Like, Compiler warnings plugin says like this. WARNINGS Parsing warnings in console log with parser GNU Make + GNU C Compiler (gcc) Because our build log is huge in size , Log parser takes ~10 min of a time to complete parsing. Some time, our developers have no clue that log parser is running or no. So providing info like this could help, Console Log Parser Parsing console log with "user_specifide_parser_file" Thanks, Bakki Environment: Jenkins , Manual installation , Cent OS 6.3 Project: Jenkins Priority: Minor Reporter: Bakkiaraj Murugesan 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-20575) Jenkins 1.539 throws lots of warnings in the log file
Bakkiaraj Murugesan closed JENKINS-20575 as Fixed Jenkins 1.539 throws lots of warnings in the log file I have upgraded to Jenkins 1.540. Now I am not seeing the reported warnings . Thanks Change By: Bakkiaraj Murugesan (22/Nov/13 5:24 AM) Status: Open Closed 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.
[JIRA] [core] (JENKINS-20575) Jenkins 1.539 throws lots of warnings in the log file
Bakkiaraj Murugesan created JENKINS-20575 Jenkins 1.539 throws lots of warnings in the log file Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 14/Nov/13 4:32 AM Description: I have recently upgraded to Jenkins 1.539. After the upgrade, I am getting too many warnings from Jetty. Here is the snip from my Jenkins.log (redirected log) -- INFO: Mars2_SW_N1b_Test #125 main build action completed: SUCCESS Nov 14, 2013 9:06:57 AM hudson.model.Run getEnvironment INFO: Changing BUILD_ID variable (job build time) with the date pattern yy_MM.dd_HH.mm. Nov 14, 2013 9:28:58 AM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.539.jar!/lib/layout/layout.jelly:75:72: st:include finished at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:25) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:63) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) 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: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.539.jar!/lib/layout/layout.jelly:75:72: st:include finished at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at
[JIRA] [nodeofflinenotification] (JENKINS-18943) Can not configure Node with Node Offline Email Notification plugin
Bakkiaraj Murugesan created JENKINS-18943 Can not configure Node with Node Offline Email Notification plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: nodeofflinenotification Created: 26/Jul/13 9:49 AM Description: Hi, When I try to add Node Offline Email Notification to existing node, (Please see screen shot) and press save, I get following exception in Jenkins web interface. --- Stack trace javax.servlet.ServletException: java.lang.AssertionError: class org.jruby.proxy.hudson.slaves.NodeProperty$Proxy3 is missing its descriptor at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:201) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) 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:96) at com.cisco.step.jenkins.plugins.people.redirector.PeopleRedirectorPlugin$1.doFilter(PeopleRedirectorPlugin.java:91) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.collabnet.auth.CNFilter.doFilter(CNFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) 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:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [nodeofflinenotification] (JENKINS-18943) Can not configure Node with Node Offline Email Notification plugin
Bakkiaraj Murugesan updated JENKINS-18943 Can not configure Node with Node Offline Email Notification plugin Screen Shot of Node configuration page Change By: Bakkiaraj Murugesan (26/Jul/13 10:20 AM) Attachment: 11.png 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] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
Bakkiaraj Murugesan commented on JENKINS-18684 Can not create new Free Style Job It turns out that my browser is a problem. I use Maxthon browser, Where I see this problem but things works very well in Chrome. This issue can be closed and I will Chrome only to configure jobs in Jenkins. 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-18749) When I create new job / configure existing job few plugins automatically gets enabled and few enabled plugins automatically gets disabled
Bakkiaraj Murugesan commented on JENKINS-18749 When I create new job / configure existing job few plugins automatically gets enabled and few enabled plugins automatically gets disabled It turns out that my browser is a problem. I use Maxthon browser, Where I see this problem but things works very well in Chrome. This issue can be closed and I will Chrome only to configure jobs in Jenkins. 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] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
Bakkiaraj Murugesan resolved JENKINS-18684 as Fixed Can not create new Free Style Job It turns out that my browser is a problem. I use Maxthon browser, Where I see this problem but things works very well in Chrome. This issue can be closed and I will Chrome only to configure jobs in Jenkins. Change By: Bakkiaraj Murugesan (18/Jul/13 4:46 AM) 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.
[JIRA] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
Bakkiaraj Murugesan commented on JENKINS-18684 Can not create new Free Style Job Hi sogabe , Yes looks like all the plugins under "Build Triggers" category causing problem for me. I have uninstalled the "Build Result Trigger" plugin, even then problem persists. I found that job configuration XML (config.xml) getting corrupted. Mainly due to Some plugins under "Build Trigger" category automatically gets enabled and previously enabled plugins gets disabled. 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] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
Bakkiaraj Murugesan updated JENKINS-18684 Can not create new Free Style Job Screen Shot of Build Trigger plugins issue Change By: Bakkiaraj Murugesan (10/Jul/13 8:13 AM) Attachment: issue_build_trigger_auto_enable.png 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] [buildresult-trigger] (JENKINS-18684) Can not create new Free Style Job
Bakkiaraj Murugesan edited a comment on JENKINS-18684 Can not create new Free Style Job Hi sogabe , Yes looks like all the plugins under "Build Triggers" category causing problem for me. I have uninstalled the "Build Result Trigger" plugin, even then problem persists. I found that job configuration XML (config.xml) getting corrupted. Mainly due to Some plugins under "Build Trigger" category automatically gets enabled and previously enabled plugins gets disabled. Please see the attachment which i just uploaded. I had "build periodically" only was enabled but when I configure build job , I see other triggers are automatically getting enabled and my original settings are lost. If I remove / disable other build triggers and set to "build periodically", I could create new job / configure existing build job. So i think it is not just one plugin issue. 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-18684) Can not create new Free Style Job
Bakkiaraj Murugesan created JENKINS-18684 Can not create new Free Style Job Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/Jul/13 5:25 AM Description: Hi, I have upgraded to Jenkins 1.522 (with latest ruby-runtime plugin). I could not create new jobs any more. 1. I tried to create new free style job 2. Job configuration page appears 3. DO some configuration (Like adding build steps) 4. Press Save , I see following exception - Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) 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:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) 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:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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:67) at
[JIRA] [core] (JENKINS-18525) Jenkins 1.520 update breaks Jenkins . Jenkins wont start
Bakkiaraj Murugesan edited a comment on JENKINS-18525 Jenkins 1.520 update breaks Jenkins . Jenkins wont start Yuu Yamashita Thanks a lot 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-18525) Jenkins 1.520 update breaks Jenkins . Jenkins wont start
Bakkiaraj Murugesan commented on JENKINS-18525 Jenkins 1.520 update breaks Jenkins . Jenkins wont start ~Yuu Yamashita Thanks a lot 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-18525) Jenkins 1.520 update breaks Jenkins . Jenkins wont start
Bakkiaraj Murugesan commented on JENKINS-18525 Jenkins 1.520 update breaks Jenkins . Jenkins wont start @https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=yyuu Yuu Yamashita, Great. Your fix in https://github.com/jenkinsci/jenkins.rb/issues/91 fixes my problem. 1. I have upgraded to Jenkins 1.521 2. Jenkins did not start - As expected 3. Removed existing ruby-runtime plugin 4. Downloaded and copied ruby-runtime plugin HPI from https://github.com/jenkinsci/jenkins.rb/issues/91 my jenkins installation 5. Jenkins 1.521 started well . Problem is fixed with ruby-runtime 0.12. Please release the ruby-runtime. 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] [coverity] (JENKINS-18559) Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3
Bakkiaraj Murugesan commented on JENKINS-18559 Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3 @ChrisWoZny, Thanks for the update. I did update from Jenkins , I overlook the release notes. 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] [coverity] (JENKINS-18559) Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3
Bakkiaraj Murugesan closed JENKINS-18559 as Fixed Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3 Since the latest version of the coverity plugin only works with Coverity Connect and this behaviour is documented. So This is not a bug really. This ticket can be closed. Change By: Bakkiaraj Murugesan (04/Jul/13 12:05 PM) Status: Open Closed 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-18525) Jenkins 1.520 update breaks Jenkins . Jenkins wont start
Bakkiaraj Murugesan commented on JENKINS-18525 Jenkins 1.520 update breaks Jenkins . Jenkins wont start I have updated to latest ruby-runtime (via jenkins plugin management page) but still jenkins is not starting. 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] [coverity] (JENKINS-18559) Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3
Bakkiaraj Murugesan created JENKINS-18559 Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3 Issue Type: Bug Assignee: Unassigned Components: coverity Created: 01/Jul/13 10:17 AM Description: Hi, I am using coverity plugin 1.2.5 and coverity IM 5.5.3. Build job failed with, FATAL: Failed to access the WSDL at: http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl. It failed with: Got http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl while opening stream from http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl. javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl. It failed with: Got http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl while opening stream from http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl. at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(Unknown Source) at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown Source) at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(Unknown Source) at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(Unknown Source) at com.sun.xml.internal.ws.client.WSServiceDelegate.init(Unknown Source) at com.sun.xml.internal.ws.client.WSServiceDelegate.init(Unknown Source) at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(Unknown Source) at javax.xml.ws.Service.init(Unknown Source) at com.coverity.ws.v5.ConfigurationServiceService.init(ConfigurationServiceService.java:42) at jenkins.plugins.coverity.CIMInstance.getConfigurationService(CIMInstance.java:195) at jenkins.plugins.coverity.CIMInstance.getStream(CIMInstance.java:292) at jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:104) at hudson.Launcher.decorateFor(Launcher.java:654) at hudson.model.Slave.createLauncher(Slave.java:353) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:631) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1576) 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: Got http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl while opening stream from http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.createReader(Unknown Source) at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(Unknown Source) ... 19 more Caused by: java.io.FileNotFoundException: http://linuxblcar.in-blr01.nxp.com:6060/ws/v5/configurationservice?wsdl at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at java.net.URL.openStream(Unknown Source) ... 21 more because v5 web services not available in Coverity IM 5.5.3. Please provide an option to choose Coverity web services version. Thanks Bakkiaraj M Project: Jenkins Priority: Major Reporter: Bakkiaraj Murugesan 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
[JIRA] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime
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.
