[JIRA] [ruby] (JENKINS-17672) jpi server fails for rvm-plugin
Eito Katagiri assigned JENKINS-17672 to Eito Katagiri jpi server fails for rvm-plugin Change By: Eito Katagiri (21/Nov/13 8:00 AM) Assignee: vivekp Eito Katagiri 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] [rvm] (JENKINS-17670) rvm-plugin failing CI
Eito Katagiri assigned JENKINS-17670 to Eito Katagiri rvm-plugin failing CI Change By: Eito Katagiri (21/Nov/13 8:01 AM) Assignee: Eito Katagiri 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] [nodejs] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Eito Katagiri assigned JENKINS-20636 to Eito Katagiri RVM and NodeJS plugins are incompatible Change By: Eito Katagiri (21/Nov/13 8:01 AM) Assignee: Eito Katagiri 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] [rvm] (JENKINS-20282) rvm plugin not being build from official github sources
Eito Katagiri assigned JENKINS-20282 to Eito Katagiri rvm plugin not being build from official github sources Change By: Eito Katagiri (21/Nov/13 8:03 AM) Assignee: Eito Katagiri 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] [rvm] (JENKINS-17671) Merge pull requests in rvm-plugin please
Eito Katagiri assigned JENKINS-17671 to Eito Katagiri Merge pull requests in rvm-plugin please Change By: Eito Katagiri (21/Nov/13 8:03 AM) Assignee: Eito Katagiri 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] [plugin] (JENKINS-15255) rvm plugin is not up to date with recent source code at github
Eito Katagiri assigned JENKINS-15255 to Eito Katagiri rvm plugin is not up to date with recent source code at github Change By: Eito Katagiri (21/Nov/13 8:03 AM) Assignee: Eito Katagiri 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] [rvm] (JENKINS-18841) Failed loading job on slave because of incorrect config.xml
Eito Katagiri assigned JENKINS-18841 to Eito Katagiri Failed loading job on slave because of incorrect config.xml Change By: Eito Katagiri (21/Nov/13 8:04 AM) Assignee: Eito Katagiri 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] [ghprb] (JENKINS-20436) Allow automatic merge after successful build
Ivaylo Bratoev assigned JENKINS-20436 to Thomas Diesler Allow automatic merge after successful build Change By: Ivaylo Bratoev (21/Nov/13 8:12 AM) Assignee: Ivaylo Bratoev Thomas Diesler 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-20630) Jenkins fails to start
heinzepreller commented on JENKINS-20630 Jenkins fails to start Same problem here, update from 1.538 to 1.540 fails on Windows x64 Server with tomcat as service. Service starts over and over again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-8756) Support multiple fetch refspecs
Paul B commented on JENKINS-8756 Support multiple fetch refspecs @Sergey Vidyuk Thanks for your little script, we are doing the same kind of thing on our PR builds. I understand the plugin doesn't need to fetch updates. But I don't understand why it would not at least try to fetch the latests changes of the PR target branch. So +1 for this 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] [prioritysorter] (JENKINS-8597) Deal with matrix builds better
Matt Gumbel commented on JENKINS-8597 Deal with matrix builds better @sven - Have you submitted that patch to them? Any idea when or if it will be available in next Jenkins release? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [custom-tools] (JENKINS-20693) Customtools fails to unpack tar.gz on os-x correctly
Anton Lundin created JENKINS-20693 Customtools fails to unpack tar.gz on os-x correctly Issue Type: Bug Assignee: Oleg Nenashev Components: custom-tools Created: 21/Nov/13 9:20 AM Description: When having a custom tool defined to download and install http://nodejs.org/dist/v0.10.22/node-v0.10.22-darwin-x64.tar.gz , it somehow fails to untar that correctly, not placing all the files in the correct subfolder, thus fails node to run correctly. When replacing the download job with a shell-part that does this manually, it works just fine. This might be a problem with the jvm/libraries outside custom tools on OS X, but i didn't manage to figure out where or what it calls, so i decided to report it here for reference. Environment: Mac OS X 10.8 Project: Jenkins Priority: Major Reporter: Anton Lundin 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-20327) javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 241320>200000
Dennys Hsieh commented on JENKINS-20327 javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 241320>20 It seems -1 doesn't work, we change to use a number and it works now. -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500 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-20664) radiator-view plugin stop work after upgrade to 1.539
David Resnick
updated JENKINS-20664
radiator-view plugin stop work after upgrade to 1.539
Change By:
David Resnick
(21/Nov/13 9:35 AM)
Description:
Goes to [https://ci.abc.local/view/Radiator/]It always
said
says
"This view has no jobs associated with it. You can either add some existing jobs to this view or create a new job in this view."But I added existing jobs and still no job is displayed on the view.
Not sure whether it's related to JENKINS-20262 or not
{noformat}Caused by: java.lang.ClassCastExceptionNov 19, 2013 7:47:10 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: it.items in /view/iOS%20Radiator/. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor305.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke
[JIRA] [core] (JENKINS-20693) Customtools fails to unpack tar.gz on os-x correctly
Oleg Nenashev updated JENKINS-20693 Customtools fails to unpack tar.gz on os-x correctly Hello, "Extract tar.gz" Installer is not a part of custom-tools plugin. It is located in Jenkins core and stored as an extension. Please specify versions of JVM and Jenkins core BR, Oleg Nenashev Change By: Oleg Nenashev (21/Nov/13 9:35 AM) Labels: installer Component/s: core 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-20693) Customtools fails to unpack tar.gz on os-x correctly
Oleg Nenashev edited a comment on JENKINS-20693 Customtools fails to unpack tar.gz on os-x correctly Hello, "Extract tar.gz" Installer is not a part of custom-tools plugin. It is located in Jenkins core and stored as an extension. Please specify versions of JVM and Jenkins core. Have you tried to unpack the referenced archive on other platforms? BR, Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14385) Jenkins stops responding after multiple chages to different jobs.
evernat commented on JENKINS-14385 Jenkins stops responding after multiple chages to different jobs. Is it reproduced with a recent Jenkins version? If yes, can you give more information, such as a threads dump? 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] [subversion] (JENKINS-19600) Subversion Plugin 1.51 consistently throws NoSuchMethodError
Kimmo Toro commented on JENKINS-19600 Subversion Plugin 1.51 consistently throws NoSuchMethodError Still getting this error with Jenkins 1.509.4 and Subversion plugin version 1.54 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] [subversion] (JENKINS-19600) Subversion Plugin 1.51 consistently throws NoSuchMethodError
Marius van Witzenburg commented on JENKINS-19600 Subversion Plugin 1.51 consistently throws NoSuchMethodError Jenkins version 1.536 and Subversion plugin 1.53 works perfectly. Seems to be fixed to 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 -- 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] [publish-over-ssh] (JENKINS-20694) When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Serv
Matthew Alder created JENKINS-20694 When attempting to connect to destination we receive: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] Issue Type: Bug Affects Versions: current Assignee: bap Components: publish-over-ssh Created: 21/Nov/13 10:13 AM Description: Jenkins is running under user account X which has permissions and trusts our destination (in its knownhosts file). Using the command line, we are able to SSH/SCP/etc. to our destination host with that account but when attempting to orchestrate exactly the same connection via the Jenkins Publish over SSH plugin, we receive the error: jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [BETA Unix Server]. Message [Auth cancel] I note that the failed login count on the destination increases. We are not using public/private key here, just password but as mentioned, it works perfectly when performed manually on the cmd line. Please could someone help us ascertain whether this is a bug or a problem with our setup? Project: Jenkins Priority: Major Reporter: Matthew Alder 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] [keyboard-shortcuts] (JENKINS-20696) Configure/edit keyboard shortcuts
Lokesh Govindu created JENKINS-20696 Configure/edit keyboard shortcuts Issue Type: New Feature Affects Versions: current Assignee: jieryn Components: keyboard-shortcuts Created: 21/Nov/13 10:23 AM Description: I have many jobs on my Jenkins-CI. I don't want shortcut 'b' to build a job. Can you give a way to user to edit/modify the keyboard shortcuts. Project: Jenkins Labels: plugin Priority: Minor Reporter: Lokesh Govindu 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] [dashboard-view] (JENKINS-20695) Dashboard view not displayed after upgrading to Jenkins 1.538
Jason Spotswood created JENKINS-20695 Dashboard view not displayed after upgrading to Jenkins 1.538 Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 21/Nov/13 10:23 AM Description: After upgrading to Jenkins 1.538, no information is displayed for dashboard based views. Downgrading to Jenkins 1.537 resolves the problem. The version of the dashboard-view plugin is 2.9.2. There were heaps of exceptions output to the logs. For instance: hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.getBuildStat(jobs) in /jenkins/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.view.dashboard.stats.StatBuilds.getBuildStat(StatBuilds.java:42) Environment: Linux RHEL 5.10 Project: Jenkins Priority: Critical Reporter: Jason Spotswood 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-20693) Customtools fails to unpack tar.gz on os-x correctly
Anton Lundin commented on JENKINS-20693 Customtools fails to unpack tar.gz on os-x correctly Master is running jenkins 1.540, Ubuntu 12.04 java -version java version "1.7.0_25" OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1ubuntu0.12.04.2) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) Mac OS X 10.8 slave: java -version java version "1.6.0_65" Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609) Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode) 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-20693) Customtools fails to unpack tar.gz on os-x correctly
Anton Lundin commented on JENKINS-20693 Customtools fails to unpack tar.gz on os-x correctly And Yes, unpacking that archive on a linux slave running the exact same setup as the master above, it works just fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20697) API wrong number of arguments on build specific endpoints
Phil Jones created JENKINS-20697 API wrong number of arguments on build specific endpoints Issue Type: Bug Assignee: Unassigned Components: core Created: 21/Nov/13 10:32 AM Description: Version 1.539 (1.540 fails to start on Windows) URL: http://192.168.1.89:8080/job/Foo%20.NET%204.5%20%28Phil%29/105/api/xml and others around specific builds Error: javax.servlet.ServletException: java.lang.IllegalArgumentException: wrong number of arguments at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) 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 org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) 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 org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) 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(Http
[JIRA] [dashboard-view] (JENKINS-20695) Dashboard view not displayed after upgrading to Jenkins 1.538
Jason Spotswood updated JENKINS-20695 Dashboard view not displayed after upgrading to Jenkins 1.538 Change By: Jason Spotswood (21/Nov/13 10:34 AM) Attachment: jenkins.log Description: After upgrading to Jenkins 1.538, no information is displayed for dashboard based views. Downgrading to Jenkins 1.537 resolves the problem.The version of the dashboard-view plugin is 2.9.2.There were heaps of exceptions output to the logs.For instance:hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: it.getBuildStat(jobs) in /jenkins/. Reason: java.lang.NullPointerExceptionjava.lang.NullPointerExceptionat hudson.plugins.view.dashboard.stats.StatBuilds.getBuildStat(StatBuilds.java:42) Reference the jenkins.log attachment for the complete exception log output. 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] [prioritysorter] (JENKINS-8597) Deal with matrix builds better
Sven Appenrodt commented on JENKINS-8597 Deal with matrix builds better No i don't. And no idea Sorry. And i afraid it will not be integrated the next time because the last action of "bklarson" is older than 1 year... 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-19099) Slow loading and large memory usage after 1.480.3 to 1.509.2 migration
Oleg Nenashev commented on JENKINS-19099 Slow loading and large memory usage after 1.480.3 to 1.509.2 migration I suppose you should provide memory dump at least. Have you updated the core to 1.509.3/4. These versions contains many fixes for lazy classloader, which may help you. 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-19099) Slow loading and large memory usage after 1.480.3 to 1.509.2 migration
Oleg Nenashev edited a comment on JENKINS-19099 Slow loading and large memory usage after 1.480.3 to 1.509.2 migration I suppose you should provide memory dump at least. Have you updated the core to 1.509.3/4? These versions contains many fixes for lazy classloader, which may help you. 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] [plugin] (JENKINS-18821) Jenkins-Plugin 3.5 working with Testlink 1.9.7 ?
Gustavo Chaves commented on JENKINS-18821 Jenkins-Plugin 3.5 working with Testlink 1.9.7 ? I'm facing the same problem here with TestLink 1.9.8, Jenkins 1.509.4, and Plugin 3.8. 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] [plugin] (JENKINS-18821) Jenkins-Plugin 3.5 working with Testlink 1.9.7 ?
Gustavo Chaves commented on JENKINS-18821 Jenkins-Plugin 3.5 working with Testlink 1.9.7 ? I just found the problem in my case. In the job configuration I had left the "TestLink Version" option as "(default)". After selecting the specific TestLink version I have configured the problem went away. I thought that since I have only one TestLink configuration I could leave it as "(default)", but it seems that it's not so. 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] [jenkins-multijob-plugin] (JENKINS-20699) NPE when MultiJobBuilder reaches a disabled job
Edmund Rhudy created JENKINS-20699 NPE when MultiJobBuilder reaches a disabled job Issue Type: Bug Assignee: Unassigned Components: jenkins-multijob-plugin Created: 21/Nov/13 2:29 PM Description: After upgrading MultiJobBuilder from 1.9 to 1.10, whenever the build process reaches a disabled job, it fails with an NPE like the one below. I'm using variously Jenkins 1.538 or 1.540, but have seen the error on both. Downgrading back to 1.9 appears to resolve the issue. Warning: can't execute one of Kill running Gradle daemons (QA2) builds, due to jenkins limitations.Starting build job Clean up repo state (QA2). FATAL: null java.lang.NullPointerException at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:121) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:70) at hudson.model.Run.execute(Run.java:1679) at hudson.model.Run.run(Run.java:1626) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:63) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Project: Jenkins Priority: Major Reporter: Edmund Rhudy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-18473) Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString()
Jesse Glick updated JENKINS-18473 Change History cosumes extreme amounts of CPU due to unnecessary usage of Fingerprint.toString() Change By: Jesse Glick (21/Nov/13 3:47 PM) Labels: performance 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] [plugin] (JENKINS-20025) Dashboard View Plugin: Starting jobs returns error 'Form post required'
Chris Bush commented on JENKINS-20025 Dashboard View Plugin: Starting jobs returns error 'Form post required' Seconded. Pretty annoying, but doesn't break functionality. 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-20630) Jenkins fails to start
Norbert Pfistner commented on JENKINS-20630 Jenkins fails to start Same to me after upgrade from 1.539 to 1.540 on Windows7 x64 I started the update by using the jenkins->configure system->automatically update feature on our runing instance. First time in several years the upgraded release is broken ... I now reverted back to 1.539 I'd like to provide a wish list concerning this bug: fix the bug home page link stable releases and label it as stable link weekly builds and label them clearly as at your own risk jenkins->configure system->update link stable release only This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18709) Support rvm plugin for building Ruby projects in RVM controlled env
Daniel Spilker resolved JENKINS-18709 as Fixed Support rvm plugin for building Ruby projects in RVM controlled env Change By: Daniel Spilker (21/Nov/13 10:08 PM) Status: Open Resolved Assignee: Justin Ryan Jens Hausherr 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] [job-dsl-plugin] (JENKINS-20687) downstream() does not support 'ALWAYS'
Daniel Spilker commented on JENKINS-20687 downstream() does not support 'ALWAYS' Arg, fixed it, too fast. BTW, you should be able to edit the wiki, so feel free to fix stuff. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18942) Job DSL should support Fingerprint Publisher
Daniel Spilker resolved JENKINS-18942 as Fixed Job DSL should support Fingerprint Publisher Change By: Daniel Spilker (21/Nov/13 10:06 PM) Status: Open Resolved Assignee: Justin Ryan wolfs 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-20532) HTTP session count
evernat resolved JENKINS-20532 as Fixed HTTP session count This is now fixed in the monitoring plugin v1.48, which was just published. The monitoring plugin v1.48 should be available in the update center of your Jenkins, or from http://mirrors.jenkins-ci.org/plugins/monitoring/, in a few hours (24h max?). Change By: evernat (21/Nov/13 10:06 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-20107) master using more executors than specified
James Theisen commented on JENKINS-20107 master using more executors than specified So ghost might not be the best description. It would operate just like a normal master executor. It would run builds, you could watch them run and see results for them. The only failure I saw out of this was I have a groovy script that monitors for hung builds and it would fail because I get the executor in that script to determine if it was a master or slave build. It would cause an exception because Jenkins saw no executor for the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18942) Job DSL should support Fingerprint Publisher
Daniel Spilker updated JENKINS-18942 Job DSL should support Fingerprint Publisher Change By: Daniel Spilker (21/Nov/13 10:06 PM) Fix Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-20687) downstream() does not support 'ALWAYS'
Mike Dougherty commented on JENKINS-20687 downstream() does not support 'ALWAYS' oh, great. i wasn't aware i had edit permissions. thanks for the info 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-20640) Jenkins become very slow and had 'proxy error'
evernat commented on JENKINS-20640 Jenkins become very slow and had 'proxy error' The related issue about HTTP sessions, JENKINS-20352, is now fixed in the monitoring plugin v1.48. The monitoring plugin v1.48 should be available in the update center of your Jenkins, or from http://mirrors.jenkins-ci.org/plugins/monitoring/, in a few hours from now (24h max?). I suggest to try that version of the plugin. But I can't say if that version will fix your issue, or if you have another bigger 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] [text-finder] (JENKINS-20704) Jenkins Text Finder is waiting for a checkpoint
Massimo Rossello created JENKINS-20704 Jenkins Text Finder is waiting for a checkpoint Issue Type: Bug Assignee: drlewis Components: text-finder Created: 21/Nov/13 4:23 PM Description: When the first of two or more concurrent plugins is slower than the following, the others cannot finish their job and free the line because they remain stuck until the first finishes. On the console of following, faster jobs it is displayed: "Jenkins Text Finder is waiting for a checkpoint" According to https://issues.jenkins-ci.org/browse/JENKINS-9913 it is a bad behavior of the plugin Environment: Jenkins 1.534 Text Finder 1.9 Project: Jenkins Labels: performance job concurrent-build Priority: Major Reporter: Massimo Rossello 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-20640) Jenkins become very slow and had 'proxy error'
evernat edited a comment on JENKINS-20640 Jenkins become very slow and had 'proxy error' The related issue about HTTP sessions, JENKINS-20352, is now fixed in the monitoring plugin v1.48. The monitoring plugin v1.48 should be available in the update center of your Jenkins, or from http://mirrors.jenkins-ci.org/plugins/monitoring/, in a few hours from now (24h max?). I suggest to try that version of the plugin. But I can't say if that version will fix your issue, or if you have another bigger issue, related to Jetty 8 or anything else. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-16362) Use XmlUnit to compare configs before saving
Daniel Spilker resolved JENKINS-16362 as Fixed Use XmlUnit to compare configs before saving Done, see https://github.com/jenkinsci/job-dsl-plugin/commit/42a9e3540719b8d597427c09234350c709e0358a. Change By: Daniel Spilker (21/Nov/13 10:14 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-19685) Add support for the Static Code Analysis Plugins in the Job-DSL
Daniel Spilker commented on JENKINS-19685 Add support for the Static Code Analysis Plugins in the Job-DSL All have been added, except for the OWASP Dependency-Check plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20532) HTTP session count
evernat commented on JENKINS-20532 HTTP session count @Dennys No, just the monitoring plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-20023) Make CLI interface help more accesible
Oliver Gondža stopped work on JENKINS-20023 Make CLI interface help more accesible Change By: Oliver Gondža (21/Nov/13 9:35 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-19685) Add support for the Static Code Analysis Plugins in the Job-DSL
wolfs commented on JENKINS-19685 Add support for the Static Code Analysis Plugins in the Job-DSL The OWASP dependency-check plugin has been added, too! See dependencyCheck! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-19685) Add support for the Static Code Analysis Plugins in the Job-DSL
wolfs closed JENKINS-19685 as Fixed Add support for the Static Code Analysis Plugins in the Job-DSL Change By: wolfs (21/Nov/13 10:25 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-20640) Jenkins become very slow and had 'proxy error'
evernat commented on JENKINS-20640 Jenkins become very slow and had 'proxy error' In the monitoring plugin, how many sessions are counted? And can you attach the image given by the following? http://localhost:8080/monitoring?part=graph&graph=httpSessions (where localhost and 8080 are the host and port of your server) 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-20703) Manage Plugins delta version direct link in column
Greg Moncreaff
created JENKINS-20703
Manage Plugins delta version direct link in column
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core, ui-changes
Created:
21/Nov/13 4:11 PM
Description:
On the Manage Plugins page, you see columns for version installed, available.
User has to go to plugin page, find changes in latest, edit the query, to compare what went in between installed and current.
This is indirect/annoying especially if more than one version exists between the two
Could you add a column with a direct URL,
e.g.
If manage plugin has row like:
[Warnings Plugin | 4.38 | 4.35]
can you add a column (header=delta {between installed/current})
https://github.com/jenkinsci/warnings-plugin/compare/warnings-4.35...warnings-4.38
not sure if plugin names and git paths are pattern suitable, or look up if not, OW this is an opportunity to regularize that too...
Project:
Jenkins
Priority:
Minor
Reporter:
Greg Moncreaff
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-19685) Add support for the Static Code Analysis Plugins in the Job-DSL
Daniel Spilker commented on JENKINS-19685 Add support for the Static Code Analysis Plugins in the Job-DSL Cool, I missed that. 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-14385) Jenkins stops responding after multiple chages to different jobs.
Kevin Thieling resolved JENKINS-14385 as Fixed Jenkins stops responding after multiple chages to different jobs. This issue does not seem to be occurring after updating Jenkins. Currently on core 1.530 Change By: Kevin Thieling (21/Nov/13 1:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-20710) Provide default configurations for Gmail and Yahoo
Harpreet Singh created JENKINS-20710 Provide default configurations for Gmail and Yahoo Issue Type: Improvement Assignee: Unassigned Components: mailer Created: 21/Nov/13 10:32 PM Description: The mail configuration can be enhanced to provide an option for GMail, Yahoo out of the box. Just provide email id and password and the SMTP configuration is setup instead of making users searching on the web for configuration options. Project: Jenkins Priority: Minor Reporter: Harpreet Singh 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] [testlink] (JENKINS-20381) ResultSeeking Strategy "jUnit Suite Name" not working
Bruno P. Kinoshita started work on JENKINS-20381 ResultSeeking Strategy "jUnit Suite Name" not working Change By: Bruno P. Kinoshita (21/Nov/13 6:57 PM) Status: Open In Progress 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] [testlink] (JENKINS-20711) Request for a TestLink / plug-in compatibility matrix update
Lisa Stanley created JENKINS-20711 Request for a TestLink / plug-in compatibility matrix update Issue Type: Bug Assignee: Bruno P. Kinoshita Components: testlink Created: 21/Nov/13 10:38 PM Description: The compatibility matrix on the wiki (https://wiki.jenkins-ci.org/display/JENKINS/TestLink+Plugin) has no information past plug-in version 3.6. I'd like to update to more recent versions of TestLink (currently at 1.9.6) and the plug-in (currently at 3.5). However, I'm not sure what is safe, especially with TestLink version 1.9.9 coming out so very recently. There is no specific issue driving this update; just a desire to keep with the latest. Recommendations? Which combinations are stable? All information is very much appreciated. Project: Jenkins Priority: Major Reporter: Lisa Stanley 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-20662) When triggering a new build from current build page, 'Next Build' isn't shown after reloading page
martin naughton commented on JENKINS-20662 When triggering a new build from current build page, 'Next Build' isn't shown after reloading page In the lastest code for jenkins i am not seeing that problem. Do you have auto enable on? Previous and next build appear. using 1.54. followed your exact instruction which were good. first one even works 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 -- 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] [testlink] (JENKINS-20584) Undefined index: testprojectid
A B commented on JENKINS-20584 Undefined index: testprojectid After installing plugin 3.8 and rolling back from jenkins 1.540 to 1.539 (that is not operational) it works properly. The tail of the log file is (so, the testprojectid undefined was not the reason of the problem): [>>][528e00c76bc71877293301][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:03] [<<][528e00c76bc71877293301][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:03][13/Nov/21 12:47:06][took 2.667758 secs] [>>][528e00ca2f7f9717818102][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:06] [<<][528e00ca2f7f9717818102][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:06][13/Nov/21 12:47:07][took 0.871649 secs] [>>][528e00cb42656609051748][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:07] [<<][528e00cb42656609051748][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:07][13/Nov/21 12:47:08][took 1.209882 secs] [>>][528e00cc86fb1877205423][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:08] [13/Nov/21 12:47:09][WARNING][][GUI] E_NOTICE Undefined index: testprojectid - in D:\ext\wamp\www\testlink\lib\api\xmlrpc\v1\xmlrpc.class.php - Line 381 [<<][528e00cc86fb1877205423][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:08][13/Nov/21 12:47:09][took 0.831893 secs] [>>][528e00cd9bfa3052761180][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:09] [13/Nov/21 12:47:10][WARNING][][GUI] E_NOTICE Undefined index: testprojectid - in D:\ext\wamp\www\testlink\lib\api\xmlrpc\v1\xmlrpc.class.php - Line 381 [13/Nov/21 12:47:10][WARNING][][GUI] E_NOTICE Undefined index: keywords - in D:\ext\wamp\www\testlink\lib\functions\testplan.class.php - Line 6699 [13/Nov/21 12:47:10][WARNING][][GUI] E_NOTICE Undefined index: keywords - in D:\ext\wamp\www\testlink\lib\functions\testplan.class.php - Line 6728 [<<][528e00cd9bfa3052761180][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:09][13/Nov/21 12:47:10][took 0.724656 secs] [>>][528e00ceb94ae414976573][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:10] [13/Nov/21 12:47:11][WARNING][][GUI] E_NOTICE Undefined index: testcaseexternalid - in D:\ext\wamp\www\testlink\lib\api\xmlrpc\v1\xmlrpc.class.php - Line 2996 [<<][528e00ceb94ae414976573][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:10][13/Nov/21 12:47:11][took 0.712995 secs] [>>][528e00cfbec9e897099259][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:11] [13/Nov/21 12:47:12][WARNING][][GUI] E_NOTICE Undefined index: testcaseexternalid - in D:\ext\wamp\www\testlink\lib\api\xmlrpc\v1\xmlrpc.class.php - Line 2996 [<<][528e00cfbec9e897099259][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:11][13/Nov/21 12:47:12][took 0.808727 secs] [>>][528e00fbb76f0597683675][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:55] [13/Nov/21 12:47:56][WARNING][][GUI] E_NOTICE Undefined index: testprojectid - in D:\ext\wamp\www\testlink\lib\api\xmlrpc\v1\xmlrpc.class.php - Line 381 [<<][528e00fbb76f0597683675][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:55][13/Nov/21 12:47:56][took 1.140015 secs] [>>][528e00fd03b68789390692][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:57] [<<][528e00fd03b68789390692][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:57][13/Nov/21 12:47:58][took 1.045095 secs] [>>][528e00fe55091803873928][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:58] [13/Nov/21 12:47:59][WARNING][][GUI] E_NOTICE Undefined index: testprojectid - in D:\ext\wamp\www\testlink\lib\api\xmlrpc\v1\xmlrpc.class.php - Line 381 [<<][528e00fe55091803873928][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:58][13/Nov/21 12:47:59][took 0.953542 secs] [>>][528e00ff6ddd8474979569][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:59] [<<][528e00ff6ddd8474979569][DEFAULT][/testlink/lib/api/xmlrpc/v1/xmlrpc.php][13/Nov/21 12:47:59][13/Nov/21 12:48:00][took 0.935126 secs] [>>][528e0116b9d0c999196616][DEFAULT][/testlink/index.php][13/Nov/21 12:48:22] [>>][528e0117aae28473254172][DEFAULT][/testlink/lib/general/navBar.php][13/Nov/21 12:48:23] [>>][528e0117aaf00517650156][DEFAULT][/testlink/lib/general/frmWorkArea.php][13/Nov/21 12:48:23] [>>][528e011982e68956557426][DEFAULT][/testlink/lib/execute/execNavigator.php][13/Nov/21 12:48:25] [
[JIRA] [cobertura] (JENKINS-20706) Support multi-configuration jobs with user-defined axes
Marc Abramowitz updated JENKINS-20706 Support multi-configuration jobs with user-defined axes TOXENV User-defined Axix Change By: Marc Abramowitz (21/Nov/13 6:32 PM) Attachment: TOXENV.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-20700) Build Result Trigger plugin only sparks job intermittently
James Short created JENKINS-20700 Build Result Trigger plugin only sparks job intermittently Issue Type: Bug Assignee: Gregory Boissinot Components: buildresult-trigger, buildresulttrigger Created: 21/Nov/13 2:30 PM Description: I have a 'setup' job that I poll in my test job using the BRT plugin. Sometimes it works (from BRT polling log): Polling started on Nov 19, 2013 6:11:23 PM Polling for the job FrameworkTests Checking changes for job Setup. Checking expected job build results for the job Setup. Checking SUCCESS Last build result for the job Setup matches the expected result SUCCESS. Job Setup is modified. Triggering a new build. Polling complete. Took 0 ms. Changes found. Scheduling a build. But sometimes, even though the Setup job ran recently, it still doesn't spark the FrameworkTests: Polling started on Nov 20, 2013 6:11:23 PM Polling for the job SCFrameworkTests Recording context. Check changes in next poll. Polling complete. Took 1 ms. No changes. Any reason why this would be intermittent? Project: Jenkins Priority: Major Reporter: James Short 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-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao updated JENKINS-20640 Jenkins become very slow and had 'proxy error' Change By: Sam Xiao (21/Nov/13 6:00 PM) Attachment: http_session.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] [core] (JENKINS-20453) Build History disappear after reload config from disk, restart/start application, and restart managed server
martin naughton commented on JENKINS-20453 Build History disappear after reload config from disk, restart/start application, and restart managed server need information than this. did you check on the file system is the build history file are there? if so are they deleted by jenkins or there some thing going in the background? more info please 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] [testlink] (JENKINS-20599) Handle several testpoints TAP result file
Bruno P. Kinoshita commented on JENKINS-20599 Handle several testpoints TAP result file Sounds like a good idea. Voted +1 for this thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18128) Filtering build queue/executors does not work in nested view
Yoichi Nakayama updated JENKINS-18128 Filtering build queue/executors does not work in nested view Change By: Yoichi Nakayama (21/Nov/13 6:17 PM) Component/s: core 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] [cobertura] (JENKINS-20706) Support multi-configuration jobs with user-defined axes
Marc Abramowitz
updated JENKINS-20706
Support multi-configuration jobs with user-defined axes
Change By:
Marc Abramowitz
(21/Nov/13 6:29 PM)
Description:
Love the Cobertura plugin!I'm using it with Python build jobs that are set up as multi-configuration jobs; there is a user-defined axis defined for TOXENV which lets me use a Python tool called tox to run for each build, a "sub-build" (forgive me if this is the wrong terminology) for each of several Python versions -- e.g.: py26, py27, py33, and pypy. Each of these Python versions is a "sub-build" of the build. Each of those sub-builds generates its own coverage.xml file.
Here is how I set up these multi-configuration jobs:
http://tox.readthedocs.org/en/latest/example/jenkins.html
The Cobertura plugin kind of works with this setup in a somewhat incomplete way.If I go to the project page, I don't see the coverage graph. If I click on "Coverage Report", then I get back the "nodata" page. I can only view coverage by drilling into each of the individual environments. For example, I can click on the most recent build and then click the "py26" sub-build and then for that I can see a coverage report.What I would really like is to also be able to see some coverage information for the overall build -- either by:1. (simpler) having the plugin pick one of the sub-builds as representative and showing that sub-build's coverage as the coverage for the overall build. At the very simplest, it could simply pick any one of the sub-builds as the coverage is sometimes slightly different for the sub-builds, but approximately the same, so showing any one is better than nothing. Fancier would be to allow the user to specify in the plugin configuration that one of the sub-builds is the one to use. For example, since I deploy to py26, that one is most important to me, so I might pick the py26 coverage as being the one to use for the overall build.2. (fancier) do some merging of the coverage across the sub-builds -- e.g.: if a line is covered in any of the sub-builds then it is considered covered. This seems tricky. Another way to handle this is to leave it up to the user. I believe that the Python "coverage" tool has a merge sub-command that lets you merge multiple runs into one (I haven't used it yet though). It might be possible for me to manually run this in my build.If you don't have time to actively work on this issue, I am open to working on it myself, especially if you can give me a little guidance of where to look and what the overall approach might be. I've already cloned the git repo and set up Netbeans and I have messed around a little with setting breakpoints and debugging but I haven't been able to figure out yet how to get it to work. I am more of a Python guy than a Jenkins guy, but if you give me some pointers, I might be able to find my way and possibly send you a pull request.I think the main problem that I discovered while debugging is that in {{CoberturaProjectAction.getLastResultBuild}} when the plugin calls {{getAction}} on my build, it gets {{null}} (instead of a {{CoberturaBuildAction}}), so it doesn't consider the build to have coverage. So even if I attempt to manually copy a coverage.xml into the build directory, the plugin still doesn't think that the build has coverage because it calls {{getAction}} and gets {{null}} instead of a {{CoberturaBuildAction}}. I am guessing that at some point, the plugin registers this action (couldn't find where) and in the multi-config job case, it probably registers the action on the sub-jobs but not the parent job. Just a guess.
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://g
[JIRA] [testlink] (JENKINS-20381) ResultSeeking Strategy "jUnit Suite Name" not working
Bruno P. Kinoshita commented on JENKINS-20381 ResultSeeking Strategy "jUnit Suite Name" not working Hi, I've successfully reproduced the issue. Somewhere from 1.40x till the current Jenkins release the test suite name is now escaped. /'s and other chars are replaced (see SuiteResult class). I'm taking a look at different options to see how we can circumvent this. Bruno 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-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
alexlombardi edited a comment on JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 When starting Jenkins after upgrading to v 1.540 (as a windows service) I get a fatal error that shuts the service down: 1) Error injecting constructor, java.lang.NoClassDefFoundError: hudson/plugins/git/browser/GitRepositoryBrowser at hudson.plugins.backlog.BacklogGitRepositoryBrowser$DescriptorImpl.(Unknown Source) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:317) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.getComponents(ExtensionList.java:149) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at org.jenkinsci.plugins.xunit.AliasInitializer.addAliases(AliasInitializer.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoClassDefFoundError: hudson/plugins/git/browser/GitRepositoryBrowser at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1128) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:704) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1299) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1355) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(Unknown Source) at hudson.plugins.backlog.BacklogGitRepositoryBrowser$DescriptorImpl.(BacklogGitRepositoryBrowser.java:104) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) ... 30 more Caused
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Shannon Kerr commented on JENKINS-20630 Jenkins fails to start @Gemini just to clarify, by "weekly builds" I was referring to the weekly Jenkins "Latest and Greatest" release in case some people didn't catch that. My only point was that, because my experience using the weekly Jenkins releases have sometimes been more hit than miss, I rely on the user evals before ever taking a weekly and if I wanted something stable, I would take the "Long-Term Support Release" that say they are "Older but stable" Jenkins releases. I don't disagree that if the Jenkins weekly builds are going to have stability issues as significant as 1.540 that a more explicit warning on the download page or changelog is warranted. I don't need it myself as I already understand that instability is very likely and the "Older bu stable" remark on the LTS download page made it clear to me that that is where the stability is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20624) TAP result seeker's include test notes adds poor values
Bruno P. Kinoshita commented on JENKINS-20624 TAP result seeker's include test notes adds poor values Perhaps we could think in some other way to extract info from the YAMLish... some DSL, or an extra option. Don't know, just food for thought 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] [cobertura] (JENKINS-20706) Support multi-configuration jobs with user-defined axes
Marc Abramowitz updated JENKINS-20706 Support multi-configuration jobs with user-defined axes Note that coverage is shown for TOXENV=py26 "sub-build" of build #25. Coverage is not shown for build #25 overall. Change By: Marc Abramowitz (21/Nov/13 6:43 PM) Attachment: TOXENV=py26 coverage results.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] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
evernat assigned JENKINS-20640 to Unassigned Jenkins become very slow and had 'proxy error' Change By: evernat (21/Nov/13 12:33 PM) Assignee: evernat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18072) Mavem module symlinks in builds history are invalid under Windows 7
Jesse Glick resolved JENKINS-18072 as Duplicate Mavem module symlinks in builds history are invalid under Windows 7 @jknudsen sounds like your issue is unrelated to this one, so please file it separately with any steps you have to reproduce. Change By: Jesse Glick (21/Nov/13 11:17 PM) Status: Reopened Resolved 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 -- 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] [master-slave] (JENKINS-20107) master using more executors than specified
martin naughton commented on JENKINS-20107 master using more executors than specified Ok so one ghost. Does the ghost mimic another another build currently running, a build going to run or a build that has run? Or is running a build on its own that will produce a build report. Say like in your picture is it build #11. Can you see the report for that build? Ghost are people that used to be there. that i am wondering about the mimicking. 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] [update-center] (JENKINS-20685) After Upgrading Jenkins It's Not Starting
Abhishek Chikane resolved JENKINS-20685 as Duplicate After Upgrading Jenkins It's Not Starting is similar to JENKINS-20630 and JENKINS-20675 Change By: Abhishek Chikane (21/Nov/13 4:10 PM) Status: Open Resolved 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 -- 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] [master-slave] (JENKINS-20107) master using more executors than specified
James Theisen commented on JENKINS-20107 master using more executors than specified No matter how man executors I set, it would always have this ghosted extra item at the bottom with no number associated with it. With version 1.537 and higher I have seen this issue just go away. Before that it was always happening. It was always 1 ghost, no more. 1 ghost more than the number of executors you configured. I do notice that even thought the ghost has gone away, jenkins routinely uses executors higher in number, and not the first several. Not sure if this is something in the priority calculations for executors or what is going on. But at least the ghost has gone away. 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-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
alexlombardi commented on JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 When starting Jenkins after upgrading to v 1.540 (as a windows service) I get a fatal error that shuts the service down: 1) Error injecting constructor, java.lang.NoClassDefFoundError: hudson/plugins/git/browser/GitRepositoryBrowser at hudson.plugins.backlog.BacklogGitRepositoryBrowser$DescriptorImpl.(Unknown Source) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:317) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.getComponents(ExtensionList.java:149) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at org.jenkinsci.plugins.xunit.AliasInitializer.addAliases(AliasInitializer.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoClassDefFoundError: hudson/plugins/git/browser/GitRepositoryBrowser at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1128) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:704) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1299) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1355) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(Unknown Source) at hudson.plugins.backlog.BacklogGitRepositoryBrowser$DescriptorImpl.(BacklogGitRepositoryBrowser.java:104) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) ... 30 more Caused by:
[JIRA] [testlink] (JENKINS-20584) Undefined index: testprojectid
A B closed JENKINS-20584 as Fixed Undefined index: testprojectid It works properly with jenkins 1.539 plugin 3.8 testlink 1.9.8 Change By: A B (21/Nov/13 1:05 PM) Status: In Progress 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-20707) NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output
Ulli Hafner edited a comment on JENKINS-20707 NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output Is this the whole stack trace? Looks like an issue in the core classloader. 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Preston Gilchrist commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. Now that we know the way to reproduce this issue is anyone working on a permanent fix? 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-20640) Jenkins become very slow and had 'proxy error'
Sam Xiao commented on JENKINS-20640 Jenkins become very slow and had 'proxy error' evernat Thanks, but I thought the HTTP session problem is different than the proxy error. Or are they actually the same or related? 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-20532) HTTP session count
Dennys Hsieh commented on JENKINS-20532 HTTP session count Since this is a Jetty's bug, does it mean that Jenkins has memory leak 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] [testlink] (JENKINS-20589) Platform not being set when updating test case result to TestLink
SCM/JIRA link daemon commented on JENKINS-20589 Platform not being set when updating test case result to TestLink Code changed in jenkins User: witokondoria Path: src/main/java/hudson/plugins/testlink/TestLinkSite.java http://jenkins-ci.org/commit/testlink-plugin/e7f2da70efae3497adaea38f6392f63cc28dfa03 Log: [FIXED JENKINS-20589] Kept previouls platform functionality in case TAP stream isnt used or doesnt have platform information 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] [testlink] (JENKINS-20589) Platform not being set when updating test case result to TestLink
SCM/JIRA link daemon commented on JENKINS-20589 Platform not being set when updating test case result to TestLink Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/hudson/plugins/testlink/TestLinkSite.java src/test/java/hudson/plugins/testlink/TestTestLinkSite.java http://jenkins-ci.org/commit/testlink-plugin/5fd0d37c2265589096791cef87322e50e37a68a6 Log: Merge pull request #12 from witokondoria/JENKINS-20589 [FIXED JENKINS-20589] Compare: https://github.com/jenkinsci/testlink-plugin/compare/6bfecb9b8594...5fd0d37c2265 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] [cobertura] (JENKINS-20706) Support multi-configuration jobs with user-defined axes
Marc Abramowitz
updated JENKINS-20706
Support multi-configuration jobs with user-defined axes
Change By:
Marc Abramowitz
(21/Nov/13 6:40 PM)
Description:
Love the Cobertura plugin!I'm using it with Python build jobs that are set up as multi-configuration jobs; there is a user-defined axis defined for TOXENV which lets me use a Python tool called tox to run for each build, a "sub-build" (forgive me if this is the wrong terminology) for each of several Python versions -- e.g.: py26, py27, py33, and pypy. Each of these Python versions is a "sub-build" of the build. Each of those sub-builds generates its own coverage.xml file. Here is how I set up these multi-configuration jobs: http://tox.readthedocs.org/en/latest/example/jenkins.htmlThe Cobertura plugin kind of works with this setup in a somewhat incomplete way.If I go to the project page, I don't see the coverage graph
(but I *do* see JUnit test results so I guess the JUnit plugin has support for multi-configuration builds)
. If I click on "Coverage Report", then I get back the "nodata" page. I can only view coverage by drilling into each of the individual environments. For example, I can click on the most recent build and then click the "py26" sub-build and then for that I can see a coverage report.What I would really like is to also be able to see some coverage information for the overall build -- either by:1. (simpler) having the plugin pick one of the sub-builds as representative and showing that sub-build's coverage as the coverage for the overall build. At the very simplest, it could simply pick any one of the sub-builds as the coverage is sometimes slightly different for the sub-builds, but approximately the same, so showing any one is better than nothing. Fancier would be to allow the user to specify in the plugin configuration that one of the sub-builds is the one to use. For example, since I deploy to py26, that one is most important to me, so I might pick the py26 coverage as being the one to use for the overall build.2. (fancier) do some merging of the coverage across the sub-builds -- e.g.: if a line is covered in any of the sub-builds then it is considered covered. This seems tricky. Another way to handle this is to leave it up to the user. I believe that the Python "coverage" tool has a merge sub-command that lets you merge multiple runs into one (I haven't used it yet though). It might be possible for me to manually run this in my build.If you don't have time to actively work on this issue, I am open to working on it myself, especially if you can give me a little guidance of where to look and what the overall approach might be. I've already cloned the git repo and set up Netbeans and I have messed around a little with setting breakpoints and debugging but I haven't been able to figure out yet how to get it to work. I am more of a Python guy than a Jenkins guy, but if you give me some pointers, I might be able to find my way and possibly send you a pull request.I think the main problem that I discovered while debugging is that in {{CoberturaProjectAction.getLastResultBuild}} when the plugin calls {{getAction}} on my build, it gets {{null}} (instead of a {{CoberturaBuildAction}}), so it doesn't consider the build to have coverage. So even if I attempt to manually copy a coverage.xml into the build directory, the plugin still doesn't think that the build has coverage because it calls {{getAction}} and gets {{null}} instead of a {{CoberturaBuildAction}}. I am guessing that at some point, the plugin registers this action (couldn't find where) and in the multi-config job case, it probably registers the action on the sub-jobs but not the parent job. Just a guess.
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
[JIRA] [config-file-provider] (JENKINS-15976) Provided maven settings.xml in maven builder is lost
Dominik Bartholdi commented on JENKINS-15976 Provided maven settings.xml in maven builder is lost I don't think there is gonna be another 1.509.* release, so yes you'll have to wait for 1.532.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-20706) Support multi-configuration jobs with user-defined axes
Marc Abramowitz updated JENKINS-20706 Support multi-configuration jobs with user-defined axes Post build actions for Cobertura and JUnit Change By: Marc Abramowitz (21/Nov/13 6:36 PM) Attachment: Post build actions.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] [core] (JENKINS-20640) Jenkins become very slow and had 'proxy error'
evernat assigned JENKINS-20640 to evernat Jenkins become very slow and had 'proxy error' Change By: evernat (21/Nov/13 12:31 PM) Assignee: evernat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18072) Mavem module symlinks in builds history are invalid under Windows 7
Joe Knudsen reopened JENKINS-18072 Mavem module symlinks in builds history are invalid under Windows 7 Still having this problem with Maven on 1.509.4 Change By: Joe Knudsen (21/Nov/13 9:11 PM) Resolution: Duplicate 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-19401) Include YAML library
Daniel Spilker commented on JENKINS-19401 Include YAML library You can use @Grab to include a YAML library in your DSL scripts, see https://github.com/jenkinsci/job-dsl-plugin/wiki/User-Power-Moves#grab-a-shared-groovy-file. @Grab(group='org.yaml', module='snakeyaml', version='1.13') 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] [testlink] (JENKINS-20711) Request for a TestLink / plug-in compatibility matrix update
Bruno P. Kinoshita resolved JENKINS-20711 as Fixed Request for a TestLink / plug-in compatibility matrix update Hi Lisa! Have a look at the updated table. Let me know if you need anything else. Thanks, Bruno Change By: Bruno P. Kinoshita (21/Nov/13 11:58 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20532) HTTP session count
evernat updated JENKINS-20532 HTTP session count chart from related issue JENKINS-20640 Change By: evernat (21/Nov/13 8:25 PM) Attachment: http_session.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] [job-dsl-plugin] (JENKINS-20687) downstream() does not support 'ALWAYS'
Daniel Spilker resolved JENKINS-20687 as Fixed downstream() does not support 'ALWAYS' Agreed, I fixed the docs. Change By: Daniel Spilker (21/Nov/13 9:53 PM) Status: Open Resolved Assignee: Justin Ryan Daniel Spilker 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] [testlink] (JENKINS-20711) Request for a TestLink / plug-in compatibility matrix update
Lisa Stanley commented on JENKINS-20711 Request for a TestLink / plug-in compatibility matrix update That's exactly what I needed! Many thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-folder] (JENKINS-18128) Filtering build queue/executors does not work in nested view
Yoichi Nakayama updated JENKINS-18128 Filtering build queue/executors does not work in nested view I've sent a pull request https://github.com/jenkinsci/jenkins/pull/1030 It also fixes similar problem with Folder under ListView Change By: Yoichi Nakayama (21/Nov/13 10:52 PM) Component/s: cloudbees-folder 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] [rvm] (JENKINS-20282) rvm plugin not being build from official github sources
Eito Katagiri closed JENKINS-20282 as Fixed rvm plugin not being build from official github sources Merged https://github.com/jenkinsci/rvm-plugin/pull/8 which seems to contain changes between 0.3 and 0.4. Change By: Eito Katagiri (21/Nov/13 3:36 PM) 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification @jgoodspeed it helps if you can reproduce the problem and are willing to run the logger (FINE in hudson.model.User). 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-20700) Build Result Trigger plugin only sparks job intermittently
James Short updated JENKINS-20700 Build Result Trigger plugin only sparks job intermittently Change By: James Short (21/Nov/13 2:56 PM) Description: I have a 'setup' job that I poll in my test job using the BRT plugin. Sometimes it works (from BRT polling log):Polling started on Nov 19, 2013 6:11:23 PMPolling for the job FrameworkTestsChecking changes for job Setup.Checking expected job build results for the job Setup.Checking SUCCESSLast build result for the job Setup matches the expected result SUCCESS.Job Setup is modified. Triggering a new build.Polling complete. Took 0 ms.Changes found. Scheduling a build.But sometimes, even though the Setup job ran recently, it still doesn't spark the FrameworkTests:Polling started on Nov 20, 2013 6:11:23 PMPolling for the job SCFrameworkTests FrameworkTests Recording context. Check changes in next poll.Polling complete. Took 1 ms.No changes.Any reason why this would be intermittent? 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] [urltrigger] (JENKINS-20712) ETag saved in config.xml but there is no flag in job web page.
Andrey Chergik
created JENKINS-20712
ETag saved in config.xml but there is no flag in job web page.
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
urltrigger
Created:
22/Nov/13 12:26 AM
Description:
Jenkins 1.540
Plugin 0.36
checkETag value is true in "config.xml":
find ./ -type f -exec grep -HIn "ETag" {} ;
./jobs/testing_job/config.xml:64: true
ETag>
but not presented at the job web page and therefore on second save action sets to false in config.xml
Project:
Jenkins
Priority:
Major
Reporter:
Andrey Chergik
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.
