[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Frank Roghair reopened JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows Using Jenkins 1.522, having issue with symlinks under windows lastFailedBuild, lastUnstableBuild lastUnsuccessfulBuild are invalid because of this the backup fails. Change By: Frank Roghair (15/Jul/13 7:45 AM) Resolution: Fixed 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] [testng] (JENKINS-18750) NPE in testng graph
Dominik Bruhn created JENKINS-18750 NPE in testng graph Issue Type: Bug Assignee: Nalin Makar Components: testng Created: 15/Jul/13 8:04 AM Description: For one of my project, the TestNG-Graph on the Project Overview does not show anymore. If I visit the URL (/job/jobid/testngreports/graph) directly, I receive the following stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NullPointerException at hudson.plugins.testng.TestNGProjectAction.populateDataSetBuilder(TestNGProjectAction.java:220) at hudson.plugins.testng.TestNGProjectAction.doGraph(TestNGProjectAction.java:123) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) at
[JIRA] [configurationslicing] (JENKINS-18751) Support Trigger from Editable E-Mail Notification plugin
Hagen Seifert created JENKINS-18751 Support Trigger from Editable E-Mail Notification plugin Issue Type: Improvement Assignee: mdonohue Attachments: Unbenannt2.png Components: configurationslicing Created: 15/Jul/13 8:42 AM Description: At the moment it's only possible to configure the normal fields using the slicing (eg. Project Recipient List or Subject). In our case it's more important to configure the Triggers. Project: Jenkins Priority: Major Reporter: Hagen Seifert 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] [tap] (JENKINS-18532) watermarks for testresults
immo Wetzel commented on JENKINS-18532 watermarks for testresults ok no problem... Usually not all test will be passed. And with watermarks or also called thresholds you can define how many tests or how great the percentage of positive tests should be to have a somehow passed result. E.g. 5% out of your test are ok to be failed. Thats the unstable threshold. The second one is the failed mark. The robot framework plugin says: Specify thresholds for marking a build unstable or passed. Thresholds are expressed in percentage of tests that passed compared to total amount of tests run. Builds with pass percentage under the blue threshold wild be marked unstable and pass percentage under yellow threshold will yield a failed 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] [maven] (JENKINS-15935) Can't build using maven 3.1.0 latest release candidate
Julian Payne commented on JENKINS-15935 Cant build using maven 3.1.0 latest release candidate I have this error with the release version of Maven 3.1.0. This is stopping us from using the latest version of Maven. 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-15935) Can't build using maven 3.1.0 latest release candidate
Julian Payne updated JENKINS-15935 Cant build using maven 3.1.0 latest release candidate Making this critical as 3.1.0 is now the latest release version of Maven. Change By: Julian Payne (15/Jul/13 9:46 AM) Priority: Major Critical 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] [jclouds-jenkins] (JENKINS-18752) NPE while provisioning a slave and the slave machine does not get destroyed after failure
Hugo Trippaers
created JENKINS-18752
NPE while provisioning a slave and the slave machine does not get destroyed after failure
Issue Type:
Bug
Assignee:
Unassigned
Components:
jclouds-jenkins
Created:
15/Jul/13 9:50 AM
Description:
When creating a slave machine i'm seeing this NPE regularly. It causes the creation of the slave to fail, but the machine is still provisioned in cloudstack. I would have expected that the machine would be detroyed once a part of the provisioning fails.
Installed version of jenkins-jclouds is 3.2.1, Jenkins is at 1.508
1 errors
Node failures:
0 errors
at com.google.common.base.Throwables.propagate(Throwables.java:160)
at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.destroyBadNodesAndPropagate(JCloudsSlaveTemplate.java:258)
at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.get(JCloudsSlaveTemplate.java:248)
at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.provisionSlave(JCloudsSlaveTemplate.java:160)
at jenkins.plugins.jclouds.compute.JCloudsCloud$2.call(JCloudsCloud.java:216)
at jenkins.plugins.jclouds.compute.JCloudsCloud$2.call(JCloudsCloud.java:213)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.jclouds.compute.RunNodesException: error running 1 node group(cloudstack-buildslave-centos6) location(2) image(b1b99bde-480d-49fa-ac64-f7fba6445cc7) size(f351015a-cd67-4680-a8c4-5dafe0c4ab04) options({taskName=bootstrap, scriptPresent=true
, userMetadata={Name=cloudstack-buildslave-centos6}})
Execution failures:
1) ExecutionException on cloudstack-buildslave-centos6-ad8:
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)
at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:134)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.NullPointerException
at org.jclouds.cloudstack.predicates.PublicIPAddressPredicates$AssociatedWithNetwork.apply(PublicIPAddressPredicates.java:43)
at org.jclouds.cloudstack.predicates.PublicIPAddressPredicates$AssociatedWithNetwork.apply(PublicIPAddressPredicates.java:34)
at com.google.common.base.Predicates$AndPredicate.apply(Predicates.java:342)
at com.google.common.collect.Iterators$8.computeNext(Iterators.java:688)
at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at com.google.common.collect.AbstractIterator.next(AbstractIterator.java:153)
at com.google.common.collect.Iterators.find(Iterators.java:761)
at com.google.common.collect.Iterables.find(Iterables.java:646)
at org.jclouds.cloudstack.functions.ReuseOrAssociateNewPublicIPAddress.findAvailableAndAssociatedWithNetwork(ReuseOrAssociateNewPublicIPAddress.java:80)
at org.jclouds.cloudstack.functions.ReuseOrAssociateNewPublicIPAddress.apply(ReuseOrAssociateNewPublicIPAddress.java:97)
at org.jclouds.cloudstack.functions.StaticNATVirtualMachineInNetwork.apply(StaticNATVirtualMachineInNetwork.java:66)
at org.jclouds.cloudstack.compute.strategy.CloudStackComputeServiceAdapter.createNodeWithGroupEncodedIntoName(CloudStackComputeServiceAdapter.java:190)
at
[JIRA] [jclouds-jenkins] (JENKINS-18753) Instance limit ignored when provisioning slaves
Hugo Trippaers created JENKINS-18753 Instance limit ignored when provisioning slaves Issue Type: Bug Assignee: Unassigned Components: jclouds-jenkins Created: 15/Jul/13 9:53 AM Description: It seems the instance limit is ignored. I'm using the jclouds plugin to create slaves and set the instance limit to 2, however it will keep starting instances up to the maximum number of instances available in that cloudstack domain. jclouds plugin version 3.2.1 jenkins version 1.508 Project: Jenkins Priority: Major Reporter: Hugo Trippaers 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-15935) Can't build using maven 3.1.0 latest release candidate
kutzi commented on JENKINS-15935 Cant build using maven 3.1.0 latest release candidate Where did you get the information about a 3.1.0 release? This page http://maven.apache.org/download.cgi still says: "Maven 3.1.0 - This is the future of Maven (alpha status)." 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-15935) Can't build using maven 3.1.0 latest release candidate
kutzi commented on JENKINS-15935 Cant build using maven 3.1.0 latest release candidate See http://osdir.com/ml/general/2013-06/msg46888.html 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-15935) Can't build using maven 3.1.0 latest release candidate
kutzi assigned JENKINS-15935 to olamy Cant build using maven 3.1.0 latest release candidate Olivier knows this stuff best Change By: kutzi (15/Jul/13 10:19 AM) Assignee: olamy 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-15935) Can't build using maven 3.1.0 latest release candidate
olamy commented on JENKINS-15935 Cant build using maven 3.1.0 latest release candidate hehe yup that need some changes... I will try to work on that end of this week. 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-15935) Can't build using maven 3.1.0 latest release candidate
Julian Payne commented on JENKINS-15935 Cant build using maven 3.1.0 latest release candidate The (alpha status) is a bug on the Maven download page - there was an alpha build available on this page but this is now the final build of 3.1.0. See http://maven.apache.org/docs/3.1.0/release-notes.html 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] [maven-repo-cleaner] (JENKINS-18754) Maven Repo Cleaner does only work for local maven repositories
Konrad Windszus created JENKINS-18754 Maven Repo Cleaner does only work for local maven repositories Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven-repo-cleaner Created: 15/Jul/13 10:37 AM Description: If the global Maven setting "Local Maven Repository" is having the value "Default (~/.m2/repository)", this plugin won't be able to clean it. Only workspace specific repositories ($WORKSPACE/.repository) are considered. Please either fix or at least document this flaw. Project: Jenkins Priority: Critical Reporter: Konrad Windszus 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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
cforce commented on JENKINS-18312 changelog browsing uses the wrong path to Redmine I am looking for a new version availabe in plugin center. Please release soon! 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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
cforce edited a comment on JENKINS-18312 changelog browsing uses the wrong path to Redmine I am looking for a new version availabe in plugin center with merged 3 month work of yoichi's and ljader's, see https://github.com/jenkinsci/redmine-plugin/network Please release more often and soon! 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-18634) HudsonAuthenticationEntryPoint can break CLI support, because the port isn't exposed properly
Luke Petre commented on JENKINS-18634 HudsonAuthenticationEntryPoint can break CLI support, because the port isnt exposed properly Updated pull request, from latest master: https://github.com/jenkinsci/jenkins/pull/850 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] [tap] (JENKINS-18703) TAP Plugin Table of Contents
Ralph Bolton commented on JENKINS-18703 TAP Plugin Table of Contents Do you have any literature about it? I've never heard about testing DNS domains :o) This is something we're trialling - the idea is to make sure that all of our domains are the same as a 'template'. For example, we make sure that certain fields in our Whois, SOA, NS and MX records have the right information in them. To do this, we give Jenkins a list of our domain names, it then runs a job that generates a series of tests for each domain, performs those tests (generating TAP output) and then reports all of that for us (and sends emails if things are wrong, etc). 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] [parameterized-trigger] (JENKINS-15476) Block until the triggered projects finish their builds doesn't notify upstream project when complete.
Yaroslav Rybak commented on JENKINS-15476 Block until the triggered projects finish their builds doesnt notify upstream project when complete. We've got this on our Jenkins ver. 1.520. Parametrized trigger plugin 2.18, linux Ubuntu 12.04 x64. 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] [xunit] (JENKINS-18755) xUnit Test Result Trend not showing
goori h created JENKINS-18755 xUnit Test Result Trend not showing Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 15/Jul/13 11:38 AM Description: Not showing Test Result Trend with boost test. Stack track javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class sun.font.FontScaler at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoClassDefFoundError: Could not initialize class sun.font.FontScaler at sun.font.TrueTypeFont.getScaler(Unknown Source) at sun.font.FileFontStrike.init(Unknown Source) at sun.font.FileFont.createStrike(Unknown Source) at sun.font.Font2D.getStrike(Unknown Source) at sun.font.Font2D.getStrike(Unknown Source) at sun.font.CompositeStrike.getStrikeForSlot(Unknown Source) at sun.font.CompositeStrike.getFontMetrics(Unknown Source) at sun.font.Font2D.getFontMetrics(Unknown Source) at java.awt.Font.defaultLineMetrics(Unknown Source) at java.awt.Font.getLineMetrics(Unknown Source) at org.jfree.chart.axis.NumberAxis.estimateMaximumTickLabelHeight(NumberAxis.java:974) at
[JIRA] [parameterized-trigger] (JENKINS-15476) Block until the triggered projects finish their builds doesn't notify upstream project when complete.
Yaroslav Rybak updated JENKINS-15476 Block until the triggered projects finish their builds doesnt notify upstream project when complete. Change By: Yaroslav Rybak (15/Jul/13 11:40 AM) Attachment: Threaddump[Jenkins].7z 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] [parameterized-trigger] (JENKINS-15476) Block until the triggered projects finish their builds doesn't notify upstream project when complete.
Yaroslav Rybak edited a comment on JENKINS-15476 Block until the triggered projects finish their builds doesnt notify upstream project when complete. We've got this on our Jenkins ver. 1.520. Parametrized trigger plugin 2.18, linux Ubuntu 12.04 x64. Attached stacktraces. 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] [cifs] (JENKINS-18019) Windows share configurations are being reset from Jenkins configuration after restart
Fred G resolved JENKINS-18019 as Duplicate Windows share configurations are being reset from Jenkins configuration after restart Change By: Fred G (15/Jul/13 11:47 AM) 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] [core] (JENKINS-18756) All builds fail with NoSuchElementException from Treemap.putAll
Maurice van der Pot created JENKINS-18756 All builds fail with NoSuchElementException from Treemap.putAll Issue Type: Bug Assignee: Unassigned Attachments: env.txt Components: core Created: 15/Jul/13 11:53 AM Description: We're experiencing failures in all our builds with the below error in console output. I've been looking at the source code of both Jenkins and Treemap itself and I can't explain how Treemap.putAll would ever generate a NoSuchElementException. For some reason this problem is 100% reproducible and dependent on (at least) the content of our junitResult.xml files in the build directories of our jobs. At the end of my debugging session I could modify the className element of one test case of one build of one job and make the problem either occur or go away. However I doubt that it has anything to do with the className element per se.I think that in this case it just happened to be the classname element of this particular build and job. I'm more inclined to believe it has to do with unsynchronized access from multiple threads. Otherwise I can't explain the exception that is thrown. We first ran into this problem with Jenkins 1.517, but we just upgraded to 1.522 and it still occurs. Am I correct in my understanding that Treemap.putAll should never generate this exception? Is this a bug? FATAL: null java.util.NoSuchElementException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1098) at java.util.TreeMap$EntryIterator.next(TreeMap.java:1136) at java.util.TreeMap$EntryIterator.next(TreeMap.java:1131) at java.util.TreeMap.buildFromSorted(TreeMap.java:2372) at java.util.TreeMap.buildFromSorted(TreeMap.java:2396) at java.util.TreeMap.buildFromSorted(TreeMap.java:2396) at java.util.TreeMap.buildFromSorted(TreeMap.java:2396) at java.util.TreeMap.buildFromSorted(TreeMap.java:2396) at java.util.TreeMap.buildFromSorted(TreeMap.java:2396) at java.util.TreeMap.buildFromSorted(TreeMap.java:2396) at java.util.TreeMap.buildFromSorted(TreeMap.java:2322) at java.util.TreeMap.putAll(TreeMap.java:296) at hudson.EnvVars.init(EnvVars.java:82) at hudson.EnvVars$GetEnvVars.call(EnvVars.java:217) at hudson.EnvVars$GetEnvVars.call(EnvVars.java:215) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.EnvVars.getRemote(EnvVars.java:212) at hudson.model.Computer.getEnvironment(Computer.java:907) at jenkins.model.CoreEnvironmentContributor.buildEnvironmentFor(CoreEnvironmentContributor.java:28) at hudson.model.Run.getEnvironment(Run.java:2046) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:933) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:84) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 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:586) at hudson.model.Run.execute(Run.java:1576) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Environment: SunOS
[JIRA] [artifactdeployer] (JENKINS-18135) Conditional Build Step plugin crashes when using Artifact Deployer plugin as build step
Kevin Phillips commented on JENKINS-18135 Conditional Build Step plugin crashes when using Artifact Deployer plugin as build step I actually posted the versions of all tools and plugins I'm using in my last comment. As for your first question, I can't speak as to the internal workings of Jenkins or these plugins. All I know is that there are two different "conditional build step" options: Conditional step (single) Conditional steps (multiple) When I create a single conditional step, I am able to choose the Artifact Deployer plugin as the "Builder" option, and saving the job configuration completes successfully. When I attempt to create a multiple job conditional step, I am still able to choose the Artifact Deployer plugin as the "Builder" option, but saving the job configuration throws an exception. I would have expected one of two things in these cases: If the Artifact Deployer plugin wasn't supported by the Conditional Build Step plugin then it shouldn't show up as a selectable option when configuring an instance of the latter. If the Artifact Deployer plugin shows up as a selectable option when creating a conditional build step, then the job configuration should save successfully and function correctly NOTE: From an end-user perspective that does not understand the internal workings of these plugins, it would also seem more intuitive that the behavior, whatever it may be, would be consistent for both the single and multi-job conditional build steps. The fact that the behavior is currently inconsistent seems odd 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] [cifs] (JENKINS-18019) Windows share configurations are being reset from Jenkins configuration after restart
Fred G commented on JENKINS-18019 Windows share configurations are being reset from Jenkins configuration after restart Same problem here. Environment: Jenkins version 1.518, Publish Over CiFS version 0.2, Jenkins Server: Win 2003 Server Seems like the configuration is not read correctly from the XML file: 15.07.2013 13:48:51 hudson.model.Descriptor load WARNUNG: Failed to load f:\Jenkins\jenkins.plugins.publish_over_cifs.CifsPublisherPlugin.xml hudson.util.IOException2: Unable to read f:\Jenkins\jenkins.plugins.publish_over_cifs.CifsPublisherPlugin.xml at hudson.XmlFile.unmarshal(XmlFile.java:170) at hudson.model.Descriptor.load(Descriptor.java:806) at jenkins.plugins.publish_over.BPPluginDescriptor.init(BPPluginDescriptor.java:56) at jenkins.plugins.publish_over_cifs.CifsPublisherPlugin$Descriptor.init(CifsPublisherPlugin.java:100) at jenkins.plugins.publish_over_cifs.CifsPublisherPlugin$Descriptor$$FastClassByGuice$$9d63b4dd.newInstance(generated) at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:259) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:59) 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:965) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961) 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:318) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1181) at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:100) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:353) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: com.thoughtworks.xstream.converters.ConversionException: object is not an instance of declaring class : object is not an instance of declaring class Debugging information message : object is not an instance of declaring class cause-exception : java.lang.IllegalArgumentException cause-message : object is not an instance of declaring class class : jenkins.plugins.publish_over_cifs.CifsHostConfiguration required-type : jenkins.plugins.publish_over_cifs.CifsHostConfiguration converter-type : hudson.util.RobustReflectionConverter path: /jenkins.plugins.publish_over_cifs.CifsPublisherPlugin$Descriptor/hostConfigurations/jenkins.plugins.publish_over_cifs.CifsHostConfiguration line number : 14 class[1]: hudson.util.CopyOnWriteList converter-type[1] : hudson.util.XStream2$AssociatedConverterImpl class[2]:
[JIRA] [cifs] (JENKINS-18019) Windows share configurations are being reset from Jenkins configuration after restart
Fred G reopened JENKINS-18019 Windows share configurations are being reset from Jenkins configuration after restart Sorry, my bad. This is not really a duplicate, because it refers to CiFS configuration not SSH. It could still be a related issue though. Change By: Fred G (15/Jul/13 12:33 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] [cifs] (JENKINS-18019) Windows share configurations are being reset from Jenkins configuration after restart
Fred G updated JENKINS-18019 Windows share configurations are being reset from Jenkins configuration after restart Change By: Fred G (15/Jul/13 12:36 PM) Component/s: publish-over-cifs 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] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
Florian Doersch edited a comment on JENKINS-18667 NullPointerException when saving job config same here but: I also get a "The job is building. Waiting for next poll." in the ScriptTrigger Log, but the job is not running. I can't even start the job anymore 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] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Adrien CLERC commented on JENKINS-17931 cvs rlog files in /tmp are not deleted Sorry for the delay, I had an extended week-end Anyway, I have no more orphaned files in /tmp right now. So it's fixed for me. Good job! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Sascha Vogt resolved JENKINS-17931 as Fixed cvs rlog files in /tmp are not deleted This has been fixed in master Resolving Change By: Sascha Vogt (15/Jul/13 1:30 PM) Status: Open Resolved Assignee: SaschaVogt 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-18756) All builds fail with NoSuchElementException from Treemap.putAll
Maurice van der Pot commented on JENKINS-18756 All builds fail with NoSuchElementException from Treemap.putAll We've noticed that running jenkins in truss can make a difference in whether or not this problem occurs. That seems to support that it is a timing issue/race condition. 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-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Jesse Glick resolved JENKINS-17571 as Duplicate The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process JNR in 1.518+ ought to help, given the reported thread dumps. Change By: Jesse Glick (15/Jul/13 2:18 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] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Jesse Glick resolved JENKINS-17681 as Fixed LastSuccessful and LastStable symlinks are invalid under Windows @frankroghair a couple of problems were fixed here. Other problems affecting certain people may well remain, but it would be better to file them separately (with whatever details to reproduce you can muster) and link to this issue. Change By: Jesse Glick (15/Jul/13 2:24 PM) Status: Reopened 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-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
dogfood commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Integrated in jenkins_main_trunk #2710 JENKINS-3265 JENKINS-17341 Even if older plugins throw an NPE during reload, continue loading job. (Revision ef08900292726bb35be269ce6d41d8dc141c6dea) Result = SUCCESS Jesse Glick : ef08900292726bb35be269ce6d41d8dc141c6dea Files : core/src/main/java/hudson/model/AbstractProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [promoted-builds] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
dogfood commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Integrated in jenkins_main_trunk #2710 JENKINS-3265 JENKINS-17341 Even if older plugins throw an NPE during reload, continue loading job. (Revision ef08900292726bb35be269ce6d41d8dc141c6dea) Result = SUCCESS Jesse Glick : ef08900292726bb35be269ce6d41d8dc141c6dea Files : core/src/main/java/hudson/model/AbstractProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-11362) Strange delay during a maven job build
Jesse Glick updated JENKINS-11362 Strange delay during a maven job build Playing with a Maven 3.1.0 upgrade but it is not trivial, due to Aether and SLF4J changes. Created maven-3.1.0 branches in lib-jenkins-maven-embedder and jenkins. @olamy do you want to pick up the rest, specifically making Maven3Builder and EmbedderLoggerImpl compilable and testing the result? Change By: Jesse Glick (15/Jul/13 3:24 PM) Assignee: JesseGlick olamy 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] [thinBackup] (JENKINS-18757) Notify user when backup is done, or provide the option of restarting Jenkins after backup
kevin ran created JENKINS-18757 Notify user when backup is done, or provide the option of restarting Jenkins after backup Issue Type: Improvement Assignee: Thomas Fürer Components: thinBackup Created: 15/Jul/13 4:04 PM Description: On the page '/thinBackup/restoreOptions' Allow the user to check an option: 'restart jenkins after restore' Kind of like the option in '/updateCenter/' Project: Jenkins Priority: Major Reporter: kevin ran 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-18683) Jenkins 1.522 config changes cannot be saved
Tomasz Oponowicz commented on JENKINS-18683 Jenkins 1.522 config changes cannot be saved Prepared pull request: https://github.com/jenkinsci/urltrigger-plugin/pull/5 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-15025) Maven-Tycho 0.15.0 build - no additional info in console log about compilation failure
Nikolas Falco commented on JENKINS-15025 Maven-Tycho 0.15.0 build - no additional info in console log about compilation failure Me too. The same problem is restricted to job of type Maven2/3. With a job of kind general and a "Maven build" step there is no problem. Reason is the different handle of Maven execution and its exception in the MavenExecutionResult object. In a job of kind general is demand to Maven executable (Embedded Maven) instead in a job of kind Maven2/3 was reimplemented by jenkins to parse informations about sub-modules. I propose a solution with this pull request https://github.com/jenkinsci/jenkins/pull/851 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] [elastic-axis] (JENKINS-18758) elastic-axis: java.lang.IllegalArgumentException when creating job
Matt Gumbel created JENKINS-18758 elastic-axis: java.lang.IllegalArgumentException when creating job Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: elastic-axis Created: 15/Jul/13 4:32 PM Description: Just upgraded to Jenkins 1.523 and am getting an exception when creating an elastic-axis job: SEVERE: Error while serving http://servername/jenkins/job/utils-configure_slaves2/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:95) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [subversion] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Greg Hansen commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request Just to close the loop, what I have found is that this issue is related to garbage collection in the underlying JVM. I installed the monitoring plugin that uses JavaMelody (see https://wiki.jenkins-ci.org/display/JENKINS/Monitoring), and if I trigger two successive garbage collections before the build of the builds run, then I don't get this error any more. (The clue came from this post: http://jenkins-ci.361315.n4.nabble.com/Hudson-garbage-collection-on-schedule-td3050696.html). From looking at the graphs generated by the plugin, what seems to happen is that if there is too much VM available, then the amount of time that garbage collection takes when it finally is triggered exceeds the amount of time required to maintain the connection to SVN. I have not characterized the times involved, just noted empirically that starting my daily builds runs with the smallest amount of VM possible seems to help a lot. Maybe there's such a thing as having too much VM? Perhaps mention of this could be made in the "setting up Jenkins" articles? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18759) Build Pipeline Plugin no longer maintaining parameters on Retry
Brian Freed created JENKINS-18759 Build Pipeline Plugin no longer maintaining parameters on Retry Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 15/Jul/13 5:11 PM Description: When using the Build Pipeline plugin up to 1.3.3 and retrying a job that had failed, the parameters that the job was originally triggered with would be applied again on the retry With version 1.3.4.1 and 1.3.5, when doing a retry, the parameters do not carry over This is a critical problem as we need this retry functionality in our pipeline Project: Jenkins Priority: Critical Reporter: Brian Freed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18759) Build Pipeline Plugin no longer maintaining parameters on Retry
Brian Freed updated JENKINS-18759 Build Pipeline Plugin no longer maintaining parameters on Retry Change By: Brian Freed (15/Jul/13 5:13 PM) Affects 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] [jclouds] (JENKINS-16945) I can't check hardware ID or Image ID from template creation
Jesse Glick commented on JENKINS-16945 I cant check hardware ID or Image ID from template creation Reproducible in Jenkins 1.520; a Stapler regression I think. 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-18592) JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520
Bruno Medeiros commented on JENKINS-18592 JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520 Same problem here: java.lang.ClassFormatError: Failed to load hudson.maven.ProcessCache$GetSystemProperties It shouldn't be related to core using Java 6, it's a separated classloader, AFAIK. 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-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Greg Hansen edited a comment on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request Just to close the loop, what I have found is that this issue is related to garbage collection in the underlying JVM. I installed the monitoring plugin that uses JavaMelody (see https://wiki.jenkins-ci.org/display/JENKINS/Monitoring), and if I trigger two successive garbage collections before the bulk of the builds run, then I don't get this error any more. (The clue came from this post: http://jenkins-ci.361315.n4.nabble.com/Hudson-garbage-collection-on-schedule-td3050696.html). From looking at the graphs generated by the plugin, what seems to happen is that if there is too much VM available, then the amount of time that garbage collection takes when it finally is triggered exceeds the amount of time required to maintain the connection to SVN. I have not characterized the times involved, just noted empirically that starting my daily builds runs with the smallest amount of VM possible seems to help a lot. Maybe there's such a thing as having too much VM? Perhaps mention of this could be made in the "setting up Jenkins" articles? 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] [thinBackup] (JENKINS-18757) Notify user when backup is done, or provide the option of restarting Jenkins after backup
Thomas Fürer commented on JENKINS-18757 Notify user when backup is done, or provide the option of restarting Jenkins after backup Thank you for your input, I will think about it and do a priorization. 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-13660) JSON fix for Opera in prototype.js probably not good anymore
Thomas Fürer closed JENKINS-13660 as Cannot Reproduce JSON fix for Opera in prototype.js probably not good anymore cannot be reproduced - environment not available anymore Change By: Thomas Fürer (15/Jul/13 6:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-15681) Support for Cloudbees Folders
Thomas Fürer assigned JENKINS-15681 to Ruben Perez Support for Cloudbees Folders Please verify and close it. thx Change By: Thomas Fürer (15/Jul/13 6:46 PM) Assignee: ThomasFürer RubenPerez 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] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
eguess74 commented on JENKINS-8963 Remote API to create/delete/modify promotions Jesse, Do you mean that each job actually requires separate "config file", not a config object? 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] [gerrit-trigger] (JENKINS-18457) Comment Added gerrit trigger doesn't work
Brian Hecko commented on JENKINS-18457 Comment Added gerrit trigger doesnt work I am also seeing this issue. I would like to be able to trigger a build once the Code Review gets a +2. 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] [translation] (JENKINS-17333) Some Spanish translations encoding mistakes
Harald Albers started work on JENKINS-17333 Some Spanish translations encoding mistakes Change By: Harald Albers (15/Jul/13 8:38 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [locale] (JENKINS-10388) Wrong french translation
Harald Albers assigned JENKINS-10388 to Harald Albers Wrong french translation Change By: Harald Albers (15/Jul/13 8:42 PM) Assignee: HaraldAlbers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-14305) Technical Version has marketing version at the beginning
evernat resolved JENKINS-14305 as Fixed Technical Version has marketing version at the beginning This is merged and supposed to be fixed, so resolving accordingly. Reopen if needed. Change By: evernat (15/Jul/13 10:10 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] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
Jesse Glick commented on JENKINS-8963 Remote API to create/delete/modify promotions No it really needs a config.xml, since this the promotion process is a distinct Job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project RTC SCM does not allow sandboxes to be nested within one another. The error indicates that the RTC repository workspace has been loaded in one directory (workspace) and the second build is trying to create a sandbox (workspace/jdk/IBM-JDK-7) within the original sandbox when doing the load. The directories are: /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/jdk/IBM-JDK-7 I am not sure if it is really your intent to have them nested, but its not supported. One option is in the Jenkins Job(s) under Advanced Project Options, check off "Use custom workspace" and specify a directory that will be a sibling of the other builds. Another option is to create a Build definition and on the Jazz Source Control tab specify the Load directory (right now its a relative path from the Jenkins Job's workspace). You might need a couple of build definitions, one for each job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-8963) Remote API to create/delete/modify promotions
eguess74 assigned JENKINS-8963 to Kohsuke Kawaguchi Remote API to create/delete/modify promotions Assigning to Kohsuke to give it a push. Change By: eguess74 (15/Jul/13 10:38 PM) Assignee: KohsukeKawaguchi 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] [assembla-auth] (JENKINS-18761) I try to install global secuirty its crash my jenkins now i can login jenkins
harpreet kang created JENKINS-18761 I try to install global secuirty its crash my jenkins now i can login jenkins Issue Type: Bug Assignee: Unassigned Attachments: jenkins error.png Components: assembla-auth Created: 15/Jul/13 10:53 PM Project: Jenkins Priority: Blocker Reporter: harpreet kang 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-18217) org.tmatesoft.svn.core.SVNException: svn: E204900
Greg Hansen commented on JENKINS-18217 org.tmatesoft.svn.core.SVNException: svn: E204900 You might look at my comment in JENKINS-13835, may be 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] [gerrit-trigger] (JENKINS-15654) Trigger on reason provided so as to change behavior for change-merged
wernight resolved JENKINS-15654 as Fixed Trigger on reason provided so as to change behavior for change-merged Yes the GERRIT_EVENT_TYPE is can help to tell that. I think I submitted this before that change. I'll try again to couple it with the Promoted Builds Plugin. Change By: wernight (15/Jul/13 11:53 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-16660) Environment variable replacement/resolving
Laurence North assigned JENKINS-16660 to Laurence North Environment variable replacement/resolving Change By: Laurence North (16/Jul/13 2:25 AM) Assignee: LaurenceNorth 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-16660) Environment variable replacement/resolving
Laurence North
commented on JENKINS-16660
Environment variable replacement/resolving
I've picked resolving this issue as an easy first contribution to Jenkins. First, I'd like to discuss backwards compatibility. Given these key,value mappings: A,a, B,b and A.B,a-b. How should $A.B and ${A.B} be evaluated? I think $A.B should evaluate to a.B, as it currently does, and ${A.B} to a-b instead of the current ${A.B}. With that scheme:
1) References to keys with dots must use brackets.
2) Existing ${A.B}-like references will break if there actually is an A.B key defined, which I think is very unlikely.
Is this an acceptable resolution?
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] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
David Turner commented on JENKINS-18667 NullPointerException when saving job config I have the same problem (GroovyScriptTrigger.getLogFile) trying to save job config. This is after updating Jenkins 1.502 to 1.523 and ScriptTrigger 0.23 to 0.29. SEVERE: Error while serving http://x:8080/jenkins/job//configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ... at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.scripttrigger.groovy.GroovyScriptTrigger.getLogFile(GroovyScriptTrigger.java:77) at org.jenkinsci.plugins.scripttrigger.groovy.GroovyScriptTrigger.getProjectActions(GroovyScriptTrigger.java:71) ... at hudson.model.Project.submit(Project.java:202) at hudson.model.Job.doConfigSubmit(Job.java:1084) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:765) ... 66 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
David Turner edited a comment on JENKINS-18667 NullPointerException when saving job config I have the same problem (GroovyScriptTrigger.getLogFile) trying to save job config. This is after updating Jenkins 1.502 to 1.523 and ScriptTrigger 0.23 to 0.29. SEVERE: Error while serving http://x:8080/jenkins/job//configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ... at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.scripttrigger.groovy.GroovyScriptTrigger.getLogFile(GroovyScriptTrigger.java:77) at org.jenkinsci.plugins.scripttrigger.groovy.GroovyScriptTrigger.getProjectActions(GroovyScriptTrigger.java:71) ... at hudson.model.Project.submit(Project.java:202) at hudson.model.Job.doConfigSubmit(Job.java:1084) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:765) ... 66 more Update: I have tried uninstalling ScriptTrigger v0.29 and reinstalling v0.28 and the last successful version v0.23, still getting the same NPE at GroovyScriptTrigger.java:77, so I suspect is is not an issue with the plugin. I will try to rollback Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-18762) Build number environment variable is not propagated when run inside a conditional build step
Davi Arnaut created JENKINS-18762 Build number environment variable is not propagated when run inside a conditional build step Issue Type: Bug Assignee: domi Components: conditional-buildstep, copyartifact Created: 16/Jul/13 5:24 AM Description: When artifacts are copied through a conditional build setup, the build number environment variable (e.g. COPYARTIFACT_BUILD_NUMBER_...) does not get propagated (or is not visible) to the remaining build steps. Project: Jenkins Priority: Major Reporter: Davi Arnaut 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.
