[JIRA] (JENKINS-16749) Exception in EmailTrigger
Christian Apel commented on JENKINS-16749 Exception in EmailTrigger In the affected build jobs, we are using an SCM trigger (scheduled SVN server polling) and the 'Build other projects' function. The exception was thrown in builds which were triggered by one of these two triggers. It was not yet thrown if a build was started manually. This message is automatically generated by JIRA. 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-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Marcel L commented on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report Hi Ogi, we face the very same issue. Version 1.0.9 works fine our paths are: JaCoCo plugin */buildReports/.exec;*/bin/debugclasses;*/src; locations are configured Cheers, Marcel This message is automatically generated by JIRA. 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-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Marcel L edited a comment on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report Hi Ogi, we face the very same issue. Version 1.0.9 works fine, our paths are: JaCoCo plugin */buildReports/.exec;*/bin/debugclasses;*/src; locations are configured Cheers, Marcel This message is automatically generated by JIRA. 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-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Marcel L edited a comment on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report Hi Ogi, we face the very same issue. Version 1.0.9 works fine, our paths are: JaCoCo plugin */buildReports/ *.exec;/bin/debugclasses;*/src; locations are configured The * is there it is just a JIRA markup issue Cheers, Marcel This message is automatically generated by JIRA. 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-16774) URLTrigger gives severe error message instead of detecting change
Magnus Jacobsson commented on JENKINS-16774 URLTrigger gives severe error message instead of detecting change What I meant was I installed Environment Injector 1.83 and then the errors were gone. I now installed URLTrigger 0.28 and it's still ok. This message is automatically generated by JIRA. 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-16785) Stacktrace after plugin installation
Markus KARG created JENKINS-16785 Stacktrace after plugin installation Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, plugin Created: 13/Feb/13 9:03 AM Description: Jenkins 1.501 was running stable / no problem is log. Then I added "JaCoCo" plugin from Update Center and restarted Jenkins. When booting, Jenkins then scared me to death with a stack trace: 13.02.2013 09:53:32 hudson.ExtensionFinder$Sezpoz scout WARNUNG: Failed to scout hudson.plugins.git.GitSCM$DescriptorImpl java.lang.InstantiationException: file:/usr/share/tomcat6/.jenkins/plugins/git/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: hudson.plugins.git.GitSCM$DescriptorImpl at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:649) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:312) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:311) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.get(ExtensionList.java:153) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1066) at hudson.maven.PluginImpl.init(PluginImpl.java:54) 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 hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.lang.ClassNotFoundException: hudson.plugins.git.GitSCM$DescriptorImpl at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:942) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 24 more Obviously it has a problem with the GIT plugin now but I didn't touch that one, and it worked well before. Also, the GIT plugin seems to work fine, still. As all works well, maybe the only bug is that the WARNING is actually printed? Environment: Jenkins 1.501 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86 IE 9 Project: Jenkins Priority: Major Reporter: Markus KARG This message is automatically generated by JIRA. 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
[JIRA] (JENKINS-16680) Downstream project being triggered twice since installing v0.11 version of plugin
Thomas Fields commented on JENKINS-16680 Downstream project being triggered twice since installing v0.11 version of plugin Hi vjuranek, Have you been able to repro this issue? Any chance of a fix? Thanks, Tom. This message is automatically generated by JIRA. 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-12188) GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace.
Andrey Upadyshev commented on JENKINS-12188 GIT plug-ins keep lock on workspace file if branch use default insted of master. So unable to clean workspace. Same problem. This is really annoying problem because it's impossible to cleanup a workspace. And after cleanup try, the Git repository became corrupted and all next builds fail until Jenkins slave service is restarted. This message is automatically generated by JIRA. 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-16298) DRY FATAL: null java.lang.StackOverflowError
Ulli Hafner commented on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError Hi Eric, I still did not manage it to reproduce the bug. Which JDK are you using? This message is automatically generated by JIRA. 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-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
SCM/JIRA link daemon resolved JENKINS-16250 as Fixed change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph Change By: SCM/JIRA link daemon (13/Feb/13 9:10 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
SCM/JIRA link daemon commented on JENKINS-16250 change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/checkstyle/CheckStyleReporter.java http://jenkins-ci.org/commit/checkstyle-plugin/e79892bdb3873059ab04ad1e0569311262353f4c Log: FIXED JENKINS-16250 Use outputFile configuration option if available. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
SCM/JIRA link daemon commented on JENKINS-16250 change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph Code changed in jenkins User: Ulli Hafner Path: plugin/clean.sh plugin/clean.sh plugin/debug.sh plugin/debug.sh plugin/german.sh plugin/german.sh plugin/go.sh plugin/go.sh plugin/pom.xml plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporter.java http://jenkins-ci.org/commit/findbugs-plugin/f31490414234f4dd64368b512fc29e521f548dfd Log: FIXED JENKINS-16250 Use outputPath configuration option if available. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-16786) Please make the N/A white, not black. :-)
Markus KARG updated JENKINS-16786 Please make the N/A white, not black. :-) Change By: Markus KARG (13/Feb/13 9:20 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. 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-16786) Please make the N/A white, not black. :-)
Markus KARG created JENKINS-16786 Please make the N/A white, not black. :-) Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 13/Feb/13 9:19 AM Description: It would be great if a future release of the JaCoCo plugin would show the dashboard "N/A" label with white background instead of that ugly black bar. As only few of my projects use JaCoCo (we have lots of non-Java project running in Jenkins) most projects now show a ugly, fat black "N/A" bar, which really scares people when looking at the dashboard. If it would have a simple white background, the "N/A" would look much more friendly. Environment: Jenkins 1.501 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86 IE 9 Project: Jenkins Priority: Trivial Reporter: Markus KARG This message is automatically generated by JIRA. 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-16787) Code coverage trend is empty if only one build exists
Markus KARG created JENKINS-16787 Code coverage trend is empty if only one build exists Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 13/Feb/13 9:25 AM Description: Obviously it is impossible to draw a trend line. But it would be great if the trend graph would not be completely empty if a job produced only one single coverage report so far, since it had only one build running yet. I want to suggest to simply draw coloured dots for each bild before drawing the trend line. In that case, even a single build's coverage result would be visible in the graph. Environment: Jenkins 1.501 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86 Project: Jenkins Priority: Minor Reporter: Markus KARG This message is automatically generated by JIRA. 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-16788) Coverage trend's legend is only partially translated
Markus KARG created JENKINS-16788 Coverage trends legend is only partially translated Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 13/Feb/13 9:30 AM Description: The JaCoCo coverage trend's legend looks like this: "- Zeilen Covered" "- Zeilen Missed" I tried to translate the page to German, but obviously one cannot translate the names "Covered" and "Missed" of the legend. It is correct that it shows "Zeilen", so somewhere must be German resources for that... Environment: Jenkins 1.501 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86 IE 9 Project: Jenkins Priority: Minor Reporter: Markus KARG This message is automatically generated by JIRA. 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-15870) Wrong port numbers in hyperlinks, case 8211
Christian Wolfgang resolved JENKINS-15870 as Incomplete Wrong port numbers in hyperlinks, case 8211 Change By: Christian Wolfgang (13/Feb/13 9:32 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. 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-15870) Wrong port numbers in hyperlinks, case 8211
Christian Wolfgang commented on JENKINS-15870 Wrong port numbers in hyperlinks, case 8211 Ok, I was a bit tired yesterday, but I'm not sure this is related to the logging plugin!? I guess I didn't read the description to careful! I'll resolve it. Please either reopen the issue again if you are sure it's about the logging plugin or change the component to the correct one. This message is automatically generated by JIRA. 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-16790) Link from Dashboard to coverage report
Markus KARG created JENKINS-16790 Link from Dashboard to coverage report Issue Type: Improvement Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 13/Feb/13 9:40 AM Description: It would be great to have a link from the dashboard's code coverage bar to the JaCoCo Coverage Report page. People tend to click on that bar to see details, but just nothing happens... Environment: Jenkins 1.501 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86 IE 9 Project: Jenkins Priority: Minor Reporter: Markus KARG This message is automatically generated by JIRA. 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-13168) NPE when Doxygen is run directly in workspace
evernat resolved JENKINS-13168 as Duplicate NPE when Doxygen is run directly in workspace Change By: evernat (13/Feb/13 9:41 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] (JENKINS-16229) Breaks CopyArtifact Plugin, case 8266
Christian Wolfgang updated JENKINS-16229 Breaks CopyArtifact Plugin, case 8266 Change By: Christian Wolfgang (13/Feb/13 9:42 AM) Summary: BreaksCopyArtifactPlugin ,case8266 This message is automatically generated by JIRA. 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-16156) Dry provides no details or paths for duplication found by Simian
Ulli Hafner resolved JENKINS-16156 as Incomplete Dry provides no details or paths for duplication found by Simian Change By: Ulli Hafner (13/Feb/13 9:42 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. 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-15989) Inconsistent display, some warnings are assigned to Default Module
Ulli Hafner commented on JENKINS-15989 Inconsistent display, some warnings are assigned to Default Module Sorry, that it took so long, I'm quite busy in the moment... What would help is to actually see what is the difference in the warnings with and without the module name. The best would be if you attach the generated XML files from my plug-in. These are located in the build folder: analysis.xml, findbugs.xml , 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] (JENKINS-12758) Jenkins looses build data on restart
evernat commented on JENKINS-12758 Jenkins looses build data on restart Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16222) Source code files for displaying warnings are empty in some cases
SCM/JIRA link daemon resolved JENKINS-16222 as Fixed Source code files for displaying warnings are empty in some cases Change By: SCM/JIRA link daemon (13/Feb/13 9:51 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16222) Source code files for displaying warnings are empty in some cases
SCM/JIRA link daemon commented on JENKINS-16222 Source code files for displaying warnings are empty in some cases Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/HealthAwareRecorder.java src/main/java/hudson/plugins/analysis/util/EncodingValidator.java src/test/java/hudson/plugins/analysis/util/EncodingValidatorTest.java http://jenkins-ci.org/commit/analysis-core-plugin/3b9fbe464d1b04c8a2520652fb94e855b8a5ba91 Log: FIXED JENKINS-16222 Ignore invalid encodings when reading files. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-12773) moving-hudson: don't delete ~hudson if it's the same as ~jenkins
evernat updated JENKINS-12773 moving-hudson: dont delete ~hudson if its the same as ~jenkins Change By: evernat (13/Feb/13 9:54 AM) Component/s: core Component/s: regexemail This message is automatically generated by JIRA. 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-15952) Checkstyle project wont transfer all files from slave to master
Ulli Hafner commented on JENKINS-15952 Checkstyle project wont transfer all files from slave to master Do you have an encoding set in the configuration screen? Seems that JENKINS-16222 is about the same problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-12773) moving-hudson: don't delete ~hudson if it's the same as ~jenkins
evernat updated JENKINS-12773 moving-hudson: dont delete ~hudson if its the same as ~jenkins Change By: evernat (13/Feb/13 9:54 AM) Assignee: justinedelson This message is automatically generated by JIRA. 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-10465) Get Support Subscription points to hudson-ci
evernat commented on JENKINS-10465 Get Support Subscription points to hudson-ci So, if you have "Get Support Subscription" in the "Manage Jenkins" page, this is a leftover in your Jenkins install from a previous Hudson install. To get rid of it, remove the directory "scis-ad" and the "scis-ad.hpi" file from "JENKINS_HOME/plugins". Then restart Jenkins. I suppose that this can be closed as "Not a defect". This message is automatically generated by JIRA. 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-10465) Get Support Subscription points to hudson-ci
evernat resolved JENKINS-10465 as Not A Defect Get Support Subscription points to hudson-ci Change By: evernat (13/Feb/13 10:02 AM) Status: Reopened Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15613) DryPublisher aborts due to exception
SCM/JIRA link daemon resolved JENKINS-15613 as Fixed DryPublisher aborts due to exception Change By: SCM/JIRA link daemon (13/Feb/13 10:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15613) DryPublisher aborts due to exception
SCM/JIRA link daemon commented on JENKINS-15613 DryPublisher aborts due to exception Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/dry/parser/DuplicationParserRegistry.java http://jenkins-ci.org/commit/dry-plugin/00eb7ca09654acd080f85381ce606197b2f8dc5b Log: FIXED JENKINS-15613 Define XML parser property so that Xerces is used. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-12758) Jenkins looses build data on restart
Lucas Clemente closed JENKINS-12758 as Fixed Jenkins looses build data on restart Works in current versions. Sorry, forgot to close it. Change By: Lucas Clemente (13/Feb/13 10:43 AM) 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] (JENKINS-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Mario Hochreiter commented on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report Hi, The same for us. Until version 1.0.9 everything worked fine. With 1.0.10 it stopped working. Maybe you should already show some error when trying to enter such a wrong Path. Cheers, Mario This message is automatically generated by JIRA. 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-16622) NPE while creating new job as copy of existing maven job
Xavier Leprévost commented on JENKINS-16622 NPE while creating new job as copy of existing maven job The version 1.501 solve my issue. This is probably related to the fix : JENKINS-16499 This message is automatically generated by JIRA. 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-16573) Getting testing result from non default junit mojo failed build.
Henrik Johansson commented on JENKINS-16573 Getting testing result from non default junit mojo failed build. Confirming the error is gone. 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] (JENKINS-15956) Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded
hagzag assigned JENKINS-15956 to Liya Katz Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded we are pending you verification Change By: hagzag (13/Feb/13 12:54 PM) Assignee: RoniLicht LiyaKatz This message is automatically generated by JIRA. 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-16791) Changelog history plugin alongside Multiple SCM plugin
David Brown created JENKINS-16791 Changelog history plugin alongside Multiple SCM plugin Issue Type: Bug Affects Versions: current Assignee: Kevin Bell Components: changelog-history, multiple-scms Created: 13/Feb/13 12:57 PM Description: Since installing the Multiple SCM plugin the changelog history plugin now shows "No changes" where previously details of changes were shown. We suspect this may be related to the "Repository browser configuration is also not supported" limitation of the Multiple SCM plugin. Can anybody suggest a workround for this? Fix Versions: current Project: Jenkins Priority: Major Reporter: David Brown This message is automatically generated by JIRA. 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-13598) jenkins-multijob-plugin - Multijob plugin throws exception when trying to get cancelled job
hagzag assigned JENKINS-13598 to Alex Nickolaevsky jenkins-multijob-plugin - Multijob plugin throws exception when trying to get cancelled job Change By: hagzag (13/Feb/13 1:04 PM) Assignee: DannyLesnik AlexNickolaevsky This message is automatically generated by JIRA. 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-16785) Stacktrace after plugin installation
emanuelez commented on JENKINS-16785 Stacktrace after plugin installation It does not look like a problem with the git plugin. It looks like some other class is asking to Jenkins about the git plugin, and Jenkins not being able to find it. It might be because this request could happen before the git plugin is actually loaded. Just my 2 cents This message is automatically generated by JIRA. 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-5677) git scm does not detect changes on master branch of upstream repo
Nicolas De Loof resolved JENKINS-5677 as Wont Fix git scm does not detect changes on master branch of upstream repo so this issue is related to the git executable version being used, that is outdated. My plan on this plugin is to get rid of git executable and use JGit, so that the plugin don't depend on git cli and has to parse console to interact with the repository, making it safer and more stable (git already changed some command options name and output format) Change By: Nicolas De Loof (13/Feb/13 1:26 PM) Status: Open Resolved Assignee: abayer NicolasDeLoof Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-10434) Git plugin 1.1.10 fails to parse author information
Nicolas De Loof resolved JENKINS-10434 as Cannot Reproduce Git plugin 1.1.10 fails to parse author information Change By: Nicolas De Loof (13/Feb/13 1:27 PM) Status: Open Resolved Assignee: abayer NicolasDeLoof Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-13157) EnvInject cannot inject variables whose contents contain a dollar sign ($)
Alexandre Zia reopened JENKINS-13157 EnvInject cannot inject variables whose contents contain a dollar sign ($) HI, I'm using EnvInject Plugin 1.62 hosted at Cloudbees and I'm having exactly this bug: EnvInject - Variables injected successfully. EnvInject - Unset unresolved 'APACHE_BASIC_AUTH_PASSWORD' variable. The parameter APACHE_BASIC_AUTH_PASSWORD contains a dolalr sign ($) which unfortunately I can't disclose here Change By: Alexandre Zia (13/Feb/13 2:01 PM) 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] (JENKINS-16784) Exception with conditional build step and inject environment variables as Builder
Magnus Jacobsson resolved JENKINS-16784 as Not A Defect Exception with conditional build step and inject environment variables as Builder This problem was probably due to incompatible Plugins and libraries manually installed. It now works as expected. Sorry for the commotion. Change By: Magnus Jacobsson (13/Feb/13 2:30 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Tim Preston commented on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report It fixed the problem for me when I entered something in the "Inclusions" section. However, I'm not too excited about having to fill this parameter in on 100+ jobs. Tim This message is automatically generated by JIRA. 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-16456) Manage launch order of jobs into a phase
hagzag resolved JENKINS-16456 as Not A Defect Manage launch order of jobs into a phase This is not a defect, by design phases will be executed in parallel. thus we cannot control their sequence especially when each job depends on a node and it's availability. Change By: hagzag (13/Feb/13 3:30 PM) Status: Open Resolved Assignee: hagzag Fix Version/s: current Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14955) Wrong links created on summary on a multijob execution
hagzag assigned JENKINS-14955 to Yoram Michaeli Wrong links created on summary on a multijob execution Please recreate and report back Change By: hagzag (13/Feb/13 3:34 PM) Assignee: YoramMichaeli This message is automatically generated by JIRA. 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-12739) Memory leak in Windows slave
Alex Vesely commented on JENKINS-12739 Memory leak in Windows slave Looks like the leak is fixed in 1.480.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] (JENKINS-15956) Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded
Liya Katz resolved JENKINS-15956 as Fixed Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded verified Change By: Liya Katz (13/Feb/13 3:59 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] (JENKINS-14583) Build number history is shared by different jobs
Bruce Adams commented on JENKINS-14583 Build number history is shared by different jobs I am still stuck with builds for different projects and/or configurations which make it look like the job is succeeding when it is failing or failing when it is succeeding because the latest build displayed on for the dashboard is in fact a completely different job. Can anyone suggest a workaround to 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] (JENKINS-12739) Memory leak in Windows slave
evernat resolved JENKINS-12739 as Fixed Memory leak in Windows slave ok, thanks. If eventually it is not fixed, feel free to reopen this issue. Change By: evernat (13/Feb/13 4:36 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] (JENKINS-16792) Debian package build plugin : Unknown option: distributor
Natalia Pokrovskaya created JENKINS-16792 Debian package build plugin : Unknown option: distributor Issue Type: Bug Assignee: Unassigned Components: plugin Created: 13/Feb/13 5:13 PM Description: Hello, I have the following problem with 'Debian package build plugin': $ bash -c 'cd "/usr/share/tomcat6/.jenkins/workspace/deb/debian" dpkg-parsechangelog -lchangelog' debian-package-builder Determined latest version to be 2.0.11 debian-package-builder Determined latest revision to be debian-package-builder No last revision known, using changes since last successful build to populate debian/changelog debian-package-builder Starting version 2.0.12.r2 with message Build #16. Started by user anonymous. debian-package-builder running command export DEBEMAIL=n...@.eu export DEBFULLNAME=Jenkins cd '/usr/share/tomcat6/.jenkins/workspace/deb/debian' dch --check-dirname-level 0 -b --distributor debian --newVersion 2.0.12.r2 'Build #16. Started by user anonymous.' ipop-deb $ /bin/sh -xe /tmp/tomcat6-tomcat6-tmp/hudson7202768819825315822.sh + export DEBEMAIL=n...@.eu + export DEBFULLNAME=Jenkins + cd /usr/share/tomcat6/.jenkins/workspace/deb/debian + dch --check-dirname-level 0 -b --distributor debian --newVersion 2.0.12.r2 Build #16. Started by user anonymous. Unknown option: distributor Usage: dch options changelog entry Run dch --help for more details debian-package-builder Aborting: Command export DEBEMAIL=n...@.eu export DEBFULLNAME=Jenkins cd '/usr/share/tomcat6/.jenkins/workspace/deb/debian' dch --check-dirname-level 0 -b --distributor debian --newVersion 2.0.12.r2 'Build #16. Started by user anonymous.' failed Build step 'Build debian package' marked build as failure Notifying upstream projects of job completion Finished: FAILURE Can I overwrite this dch command and use it without --distributor option? Or, may be, my jenkins job is not configured properly? Can anybody help my please? Thank you in advance! Environment: Debian 6.0 64bit Project: Jenkins Priority: Major Reporter: Natalia Pokrovskaya This message is automatically generated by JIRA. 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-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Ognjen Bubalo updated JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report I created a quickfix, please test it before I release it. To test the build: Stop the Jenkins instance. In the Jenkins\plugins\ delete the jacoco dir, jacoco.hpi and create an empty "jacoco.hpi.pinned" file. Then copy this .hpi file into the plugins dir and lunch Jenkins. Change By: Ognjen Bubalo (13/Feb/13 5:24 PM) Attachment: jacoco.hpi This message is automatically generated by JIRA. 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-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Ognjen Bubalo started work on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report Change By: Ognjen Bubalo (13/Feb/13 5:29 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] (JENKINS-16793) badges which appear in the build history, needs to be optional
George Kinlay created JENKINS-16793 badges which appear in the build history, needs to be optional Issue Type: Improvement Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 13/Feb/13 5:39 PM Description: Feature added in version 2.1 Add badges which appear in the build history when the configuration of the respective job has changed since it was build the last time. This needs to be optional , there is no need for builder to see this icon it just confuses him Project: Jenkins Priority: Major Reporter: George Kinlay This message is automatically generated by JIRA. 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-16794) Images served with an expires with the wrong date
scooper4711 created JENKINS-16794 Images served with an expires with the wrong date Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: infrastructure Created: 13/Feb/13 5:56 PM Description: We've been noticing heavy traffic from some users/some browsers. They request and re-request the same image files. I believe that the issue lies in the incorrect "Expires:" header returned. When requesting e.g. yellow.png the headers returned are e.g: Date: Wed, 13 Feb 2013 17:39:46 GMT Expires: Thu, 13 Feb 2014 17:39:46 GMT You'll notice that the day of the week changes, but the actual date and time is the same for the Date and the Expires. Some browsers seem to cache this OK, others seem to ignore the Expires and re-request the image. Project: Jenkins Priority: Major Reporter: scooper4711 This message is automatically generated by JIRA. 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-12010) manager.buildSuccess() doesn't work
Kevin Binswanger commented on JENKINS-12010 manager.buildSuccess() doesnt work I have the exact use case as Trevor Baker. This message is automatically generated by JIRA. 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-8666) Matrix project index page broken by axis with empty values
Jonathan Daugherty commented on JENKINS-8666 Matrix project index page broken by axis with empty values I also reproduced this with Jenkins 1.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] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
mkinzie commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs I think the ArrayIndexOutOfBoundsException on AbstractLazyLoadRunMap is being displayed prior to, and in place of the real error in some instances. I just updated to Jenkins version 1.501, and it had been probably 6 months since we had previously updated, and as soon as I did, I got the aforementioned error - all builds failed immediately because of this. It turned out the real reason for the failure was that we're using the Git Plugin, and had a bad path specified to the git executable. Fixing that fixed everything - but you couldn't tell that that's what the problem was, because instead of getting an error that it couldn't find git, it just spit out the array out of bounds stack trace. This message is automatically generated by JIRA. 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-16795) Build status changes should not be restricted to only get worse
Kevin Binswanger created JENKINS-16795 Build status changes should not be restricted to only get worse Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 13/Feb/13 7:04 PM Description: hudson.model.Run#setResult(Result r) will not set the status if the new status is worse than the existing one. I want to be able to use Groovy Postbuild Plugin to "fail out" of the job to end prematurely, but set the build as a success. For certain tool results, I want to skip the rest of the build process, but not trigger a failure. See issue #12010 Project: Jenkins Priority: Minor Reporter: Kevin Binswanger This message is automatically generated by JIRA. 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-12010) manager.buildSuccess() doesn't work
Kevin Binswanger commented on JENKINS-12010 manager.buildSuccess() doesnt work I've filed an issue against the core component https://issues.jenkins-ci.org/browse/JENKINS-16795 This message is automatically generated by JIRA. 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-14739) EnvInject params are overwritten by default string params
Daniel Beck edited a comment on JENKINS-14739 EnvInject params are overwritten by default string params This looks to me like it works as intended. The parameterized trigger only passes actual build parameters, not all variables defined as environment variables. In many of my builds, I have a few parameters at most, and often dozens of environment variables to configure generic build scripts to the specific job (like paths to certain programs in specific versions). Please also note that many other environment variables exist by default, or are defined and redefined in the global Jenkins configuration and slave configuration. And passing PATH would quickly wreck havoc on downstream builds running on different machines. An easy workaround for this issue also exists: Just add a "predefined parameters" element from the parameterized build trigger plugin, and enter PARAM_SLAVE=$PARAM_SLAVE to override the default value of the slave. Skip the "current build parameters" entirely, it's simply not what you want. This message is automatically generated by JIRA. 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-14739) EnvInject params are overwritten by default string params
Daniel Beck commented on JENKINS-14739 EnvInject params are overwritten by default string params This looks to me like it works as intended. The parameterized trigger only passes actual build parameters, not variables defined as environment variables. In many of my builds, I have a few parameters at most, and often dozens of environment variables to configure generic build scripts to the specific job (like paths to certain programs in specific versions). An easy workaround for this issue also exists: Just add a "predefined parameters" element from the parameterized build trigger plugin, and enter PARAM_SLAVE=$PARAM_SLAVE to override the default value of the slave. Skip the "current build parameters" entirely, it's simply not what you want. This message is automatically generated by JIRA. 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-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Jose Sa commented on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 I managed to perform the upgrade without failing to load jobs by disabling the Downstream buildview plugin. Maybe this info will help others with similar situation. This message is automatically generated by JIRA. 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-15533) Jobs disappearing with Jenkins 1.485 and 1.486
Jose Sa edited a comment on JENKINS-15533 Jobs disappearing with Jenkins 1.485 and 1.486 I managed to perform the upgrade to 1.501 without failing to load jobs by disabling the Downstream buildview plugin. Maybe this info will help others with similar situation. This message is automatically generated by JIRA. 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-16795) Build status changes should not be restricted to only get worse
Kevin Binswanger commented on JENKINS-16795 Build status changes should not be restricted to only get worse https://issues.jenkins-ci.org/browse/JENKINS-1201 This message is automatically generated by JIRA. 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-16795) Build status changes should not be restricted to only get worse
Kevin Binswanger edited a comment on JENKINS-16795 Build status changes should not be restricted to only get worse https://issues.jenkins-ci.org/browse/JENKINS-12010 This message is automatically generated by JIRA. 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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Alex, thanks for the suggestion. I tried out the workaround and you are right that the FILE token allows for nested content. However, when the nested content is a FILE token that uses an environment variable in the "path", it does not evaluate the environment variable. So the same problem occurs. Nesting does not rectify the problem. I think the issue is inherent in the FILE token interpretation itself. This message is automatically generated by JIRA. 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-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option
Jesse Glick commented on JENKINS-9679 NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option @marscher this was already backported to the stable branch (as 7bc441d); 1.480.3 has just not been released yet. This message is automatically generated by JIRA. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
That's not what I was trying to recommend, let me try and rephrase.
1) Create a build step that creates a file in the workspace like this:
echo ${FILE, path="%PATH_TO_FILE%"} staticname.txt
2) Use the following as the token in the email
${FILE, path="staticname.txt"}
The staticname.txt does not use a variable since you know the name of the file you are creating.
This message is automatically generated by JIRA.
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-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
SCM/JIRA link daemon commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html war/pom.xml http://jenkins-ci.org/commit/jenkins/4b1a95f23f19c57d8cf48ea0b1b30aaee541db27 Log: FIXED JENKINS-16474 Fixed the HTTP request thread saturation problem with Winstone. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-7032) Trac plugin creates wrong links
Gerd Zanker resolved JENKINS-7032 as Fixed Trac plugin creates wrong links Merged with pull request #5 into trac master branch. Change By: Gerd Zanker (13/Feb/13 7:36 PM) Status: InProgress 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] (JENKINS-13366) Prefix or truncate the file path of a change set to build Trac source browser URL
Gerd Zanker resolved JENKINS-13366 as Fixed Prefix or truncate the file path of a change set to build Trac source browser URL Merged with pull request #5 into trac master branch. Change By: Gerd Zanker (13/Feb/13 7:36 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] (JENKINS-13366) Prefix or truncate the file path of a change set to build Trac source browser URL
Gerd Zanker stopped work on JENKINS-13366 Prefix or truncate the file path of a change set to build Trac source browser URL Change By: Gerd Zanker (13/Feb/13 7:35 PM) Status: InProgress 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] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Hi Alex. I tried Step 1) that you've listed above but I get a "bad substitution" shell error and the build is marked as failed as a result. I don't think I can use the FILE token outside of the editable e-mail notification, should I be able to? Here is my syntax:
echo ${FILE,path="$MY_FILE_PATH"} staticname.txt
where "MY_FILE_PATH" is an environment variable that I've specified in a property file that I've defined as part of "Prepare an environment for the run".
This message is automatically generated by JIRA.
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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
edited a comment on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Hi Alex. I tried Step 1) that you've listed above but I get a "bad substitution" shell error and the build is marked as failed as a result. I don't think I can use the FILE token outside of the editable e-mail notification, should I be able to? Here is my syntax:
echo ${FILE, path="$MY_FILE_PATH"} staticname.txt
where "MY_FILE_PATH" is an environment variable that I've specified in a property file that I've defined as part of "Prepare an environment for the run".
This message is automatically generated by JIRA.
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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Depending on what OS you are running on, you may need to escape the writing of the token to the file. I don't what the token to be replaced, I just want you to write it out to the file when you know the path to the file you want included in the email. The idea is to write the content you want ${FILE, path="custom_info.txt"}, when custom_info.txt is in your MY_FILE_PATH variable. You would want to escape the first $ in the token while writing it out to the file.
Build step:
echo \${FILE, path="$MY_FILE_PATH"} staticname.txt
Email content:
${FILE, path="staticname.txt"}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16696) Integration test results not displayed since 1.500
Guillaume Bilodeau commented on JENKINS-16696 Integration test results not displayed since 1.500 I just installed the snapshot release you recommended and the problem seems to be fixed. 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] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Ah I see. When I escaped the first $ in the token token, this is what gets displayed in the e-mail:
${FILE, path=custom_info.txt}
So even though MY_FILE_PATH is properly evaluated to be "custom_info.txt", it looks like the nested functionality isn't working for me because it isn't evaluating "${FILE, path=custom_info.txt}" to display the contents of custom_info.txt.
The contents of staticname.txt is also:
${FILE, path=custom_info.txt}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
edited a comment on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Ah I see. When I escaped the first $ in the token, this is what gets displayed in the e-mail:
${FILE, path=custom_info.txt}
So even though MY_FILE_PATH is properly evaluated to be "custom_info.txt", it looks like the nested functionality isn't working for me because it isn't evaluating "${FILE, path=custom_info.txt}" to display the contents of custom_info.txt.
The contents of staticname.txt is also:
${FILE, path=custom_info.txt}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable You may need more escaping for the ", play around with it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13372) Add process last N builds for trend to Configure System Jenkns page.
Craig de Stigter commented on JENKINS-13372 Add process last N builds for trend to Configure System Jenkns page. +1 In addition to performance improvements, this would really make trend graphs much more useful, since it's hard to get any meaningful information from a graph that looks like this: http://i.imgur.com/HUz9FKi.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] (JENKINS-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report
Marcel L commented on JENKINS-16777 ArrayIndexOutOfBoundsException when trying to publish the Jacoco report No joy with the hotfix version: [JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] **/buildReports/*.exec;**/bin/debugclasses;**/src; locations are configured [JaCoCo plugin] Number of found exec files: 1 [JaCoCo plugin] Saving matched execfiles: /Hidden/buildReports/jacoco.exec [JaCoCo plugin] Saving matched class directories: /Hidden/bin/debugclasses [JaCoCo plugin] Saving matched source directories: /Hidden/src [JaCoCo plugin] Loading inclusions files.. ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception java.lang.ArrayIndexOutOfBoundsException: 0 at hudson.plugins.jacoco.ExecutionFileLoader.analyzeStructure(ExecutionFileLoader.java:127) at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:143) at hudson.plugins.jacoco.JacocoBuildAction.getJacocoReports(JacocoBuildAction.java:249) at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:332) at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:313) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:363) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.ivy.IvyModuleSetBuild$RunnerImpl.post2(IvyModuleSetBuild.java:587) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1593) at hudson.model.Run.run(Run.java:1514) at hudson.ivy.IvyModuleSetBuild.run(IvyModuleSetBuild.java:282) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Recording fingerprints But I can confirm Tims workaround (entered something in the "Inclusions" section). Then the project builds fine but the build becomes unstable due to jacoco. Can someone tell me why ? Recording test results [JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] **/buildReports/*.exec;**/bin/debugclasses;**/src; locations are configured [JaCoCo plugin] Number of found exec files: 1 [JaCoCo plugin] Saving matched execfiles: /Hidden/buildReports/jacoco.exec [JaCoCo plugin] Saving matched class directories: /Hidden/bin/debugclasses [JaCoCo plugin] Saving matched source directories: /Hidden/src [JaCoCo plugin] Loading inclusions files.. [JaCoCo plugin] inclusions: [**/*.class] [JaCoCo plugin] exclusions: [] [JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=100, minMethod=0, maxMethod=70, minLine=0, maxLine=80, minBranch=0, maxBranch=80, minInstruction=0, maxInstruction=80, minComplexity=0, maxComplexity=80] [JaCoCo plugin] Publishing the results.. [JaCoCo plugin] Loading packages.. [JaCoCo plugin] Done. Build step 'Record JaCoCo coverage report' changed build result to UNSTABLE Finished: UNSTABLE This message is automatically generated by JIRA. 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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Success! Thanks for the workaround Alex! I will use it . Here's the build step that worked for me (I'm running on Linux with the default shell):
echo "\${FILE,path=\"$MY_FILE_PATH\"}" staticname.txt
I still think it would be nice to have the FILE token evaluate the environment variable specified in its "path" itself as that would avoid the extra build step, but for now, this workaround does what I want it to do.
Thanks again for your quick response and help!
This message is automatically generated by JIRA.
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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable I'll leave this open and see if its something that I can add. It becomes less of a priority with the workaround, but I can see where it would be useful. This message is automatically generated by JIRA. 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-14728) Buil-flow jobs fail to load the job history if the envinject plugin is installed
Andrei Ababei closed JENKINS-14728 as Fixed Buil-flow jobs fail to load the job history if the envinject plugin is installed Change By: Andrei Ababei (13/Feb/13 9:58 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] (JENKINS-15490) Analysis parsers don't work with maven 2 jobs
Ulli Hafner commented on JENKINS-15490 Analysis parsers dont work with maven 2 jobs I tried some ideas to get the plug-in correctly running with maven 2, however nothing worked. I think that this actually is a problem in the classloader of the maven 2 plug-in in Jenkins core... Seems that they are new isolated enough. This message is automatically generated by JIRA. 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-15490) Analysis parsers don't work with maven 2 jobs
Ulli Hafner updated JENKINS-15490 Analysis parsers dont work with maven 2 jobs Change By: Ulli Hafner (13/Feb/13 10:13 PM) Component/s: maven Component/s: maven2 Component/s: analysis-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] (JENKINS-15344) ClassCastException when reports are created with maven-site-plugin
Ulli Hafner commented on JENKINS-15344 ClassCastException when reports are created with maven-site-plugin I tried some ideas to get the plug-in correctly running with new site plugin, however nothing worked. I think that this actually is a problem in the class loaders of the maven plug-in in Jenkins core... Seems that they are new isolated enough. This message is automatically generated by JIRA. 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-12785) Groovy script console SCMTrigger example causes invalid configurationw
evernat updated JENKINS-12785 Groovy script console SCMTrigger example causes invalid configurationw Change By: evernat (13/Feb/13 10:39 PM) Assignee: BaptisteMathus This message is automatically generated by JIRA. 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-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
SCM/JIRA link daemon commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) Code changed in jenkins User: Kohsuke Kawaguchi Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/c01281bdfa4ee88c5860291ef6bdda899a242e7f Log: FIXED JENKINS-16474 Fixed the HTTP request thread saturation problem with Winstone. (cherry picked from commit 4b1a95f23f19c57d8cf48ea0b1b30aaee541db27) Conflicts: changelog.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] (JENKINS-15156) Builds disappear from build history after completion
Jesse Glick commented on JENKINS-15156 Builds disappear from build history after completion @richardm_tx: 1.502 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] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
dogfood commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 Integrated in jenkins_main_trunk #2274 Result = SUCCESS This message is automatically generated by JIRA. 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-16696) Integration test results not displayed since 1.500
dogfood commented on JENKINS-16696 Integration test results not displayed since 1.500 Integrated in jenkins_main_trunk #2274 Changelog for JENKINS-16696 (Revision 027931a8a123cb866279ba98609137816a41d40a) Result = SUCCESS Christoph Kutzinski : 027931a8a123cb866279ba98609137816a41d40a Files : changelog.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] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
dogfood commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) Integrated in jenkins_main_trunk #2274 Result = SUCCESS This message is automatically generated by JIRA. 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-16561) Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull
dogfood commented on JENKINS-16561 Jelly form control f:validateButton giving a warning popup in IE irrespective of whether validation is successfull Integrated in jenkins_main_trunk #2274 Result = SUCCESS This message is automatically generated by JIRA. 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-16796) Git fails to collect commits during build
Ajith Thampi created JENKINS-16796 Git fails to collect commits during build Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 13/Feb/13 11:24 PM Description: I recently came upon to notice that certain commits are missing from the build. Git is able to collect the commits that have gone after the missed commit and there is no way to pull in that change. There was specific issues with jenkins environment where jenkins would stall because of Permgen Space errors. I am not sure if these commits got lost during this dead zone time. But regardless, there should be a way to make sure that all commits are pulled for the build. I could probably reset the project itself, but then I tend to lose the All Changes Commit information which is not ideal here. Environment: Ubuntu 12, running on AWS Project: Jenkins Priority: Major Reporter: Ajith Thampi This message is automatically generated by JIRA. 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-16794) Images served with an expires with the wrong date
Jesse Glick resolved JENKINS-16794 as Cannot Reproduce Images served with an expires with the wrong date I guess you missed that the Expires header is a year in the future. Browsers ought to load such images from cache until Jenkins is restarted (or a year passes). If you see otherwise, please provide details to reproduce—Jenkins version, browser version, sequence of steps. Change By: Jesse Glick (13/Feb/13 11:45 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16796) Git fails to collect commits during build
Ajith Thampi updated JENKINS-16796 Git fails to collect commits during build Change By: Ajith Thampi (14/Feb/13 12:04 AM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
