[JIRA] (JENKINS-16851) Strategy GerritTrigger missing with git plugin 1.1.28
Björn Pedersen commented on JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 The infinite loop could be: https://issues.jenkins-ci.org/browse/JENKINS-16849 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16871) Inconsistent use of XML escaping in config.xml
Magnus Jacobsson created JENKINS-16871 Inconsistent use of XML escaping in config.xml Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Feb/13 8:09 AM Description: When saving a job configuration, some characters are XML-escaped, e.g. the phrase 'echo "Hello World"' is stored as 'echo "Hello World"'. If this XML-file is uploaded to Jenkins through the http://myjenkinsserver/createItem API, the escaping is removed. If the job is run or manually configured and saved, the escaping comes back This causes among other things a lot of confusion when comparing different versions of the config file, either through the Jenkins Job History feature or through a version control system if the configs are stored there. Environment: Ubuntu 10.04, Jenkins 1.501 Project: Jenkins Priority: Minor Reporter: Magnus Jacobsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16871) Inconsistent use of XML escaping in config.xml when uploading through API
Magnus Jacobsson updated JENKINS-16871 Inconsistent use of XML escaping in config.xml when uploading through API Change By: Magnus Jacobsson (19/Feb/13 8:12 AM) Summary: Inconsistent use of XML escaping in config.xml when uploading through API Description: When saving a job configuration, some characters are XML-escaped, e.g. the phrase 'echo "Hello World"' is stored as 'echo "Hello World"'.If this XML-file is uploaded to Jenkins through the http://myjenkinsserver/createItem API, the escaping is removed. If the job is run or manually configured and saved, the escaping comes backThis causes among other things a lot of confusion when comparing different versions of the config file, either through the Jenkins Job History feature or through a version control system if the configs are stored there. The XML-escaping is not necessary, although not incorrect. A consistent way of handling it would however be preferred. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16871) Inconsistent use of XML escaping in config.xml when uploading through API
Magnus Jacobsson updated JENKINS-16871 Inconsistent use of XML escaping in config.xml when uploading through API Change By: Magnus Jacobsson (19/Feb/13 8:29 AM) Description: When saving a job configuration, some characters are XML-escaped, e.g. the phrase 'echo "Hello World"' is stored as 'echo & amp; quot;Hello World& amp; quot;'.If this XML-file is uploaded to Jenkins through the http://myjenkinsserver/createItem API, the escaping is removed. If the job is run or manually configured and saved, the escaping comes backThis causes among other things a lot of confusion when comparing different versions of the config file, either through the Jenkins Job History feature or through a version control system if the configs are stored there.The XML-escaping is not necessary, although not incorrect. A consistent way of handling it would however be preferred. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-7188) Configure JIRA regexp to report for each proyect
Fernando Rosado Altamirano closed JENKINS-7188 as Won't Fix Configure JIRA regexp to report for each proyect This improvement will add a lot of complexity to project management. Change By: Fernando Rosado Altamirano (19/Feb/13 8:28 AM) Status: Open Closed Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14447) Clone on Slave Fails
Martin Wiklundh commented on JENKINS-14447 Clone on Slave Fails Got the same problem on 1.492 with a job that has been working fine for long. Restarting the slave solved the problem for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16871) Inconsistent use of XML escaping in config.xml when uploading through API
Magnus Jacobsson commented on JENKINS-16871 Inconsistent use of XML escaping in config.xml when uploading through API The escaping is in effect when viewing this report. I've escaped the &-characters in the description so that the view shows the actual text. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-14746) Use nothing to build (grey builds) if there is no new baselines
Jens Brejner assigned JENKINS-14746 to Praqma Support Use nothing to build (grey builds) if there is no new baselines our case 6843 Change By: Jens Brejner (19/Feb/13 8:49 AM) Assignee: Bue Petersen Praqma Support This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-14746) Use nothing to build (grey builds) if there is no new baselines, our case 8676
Jens Brejner updated JENKINS-14746 Use nothing to build (grey builds) if there is no new baselines, our case 8676 pseudo-linking to our internal tracker Change By: Jens Brejner (19/Feb/13 8:52 AM) Summary: Use nothing to build (grey builds) if there is no new baselines , our case 8676 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Sorry to bother you again with such a stupid question: But how do I enable this? I know that I have to add this line to the java arguments: -Dmail.debug=true But I don't see where. Do I have to put it under /etc/defaults/jenkins or unter /etc/init.d/jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14746) Use nothing to build (grey builds) if there is no new baselines, our case 6843
Jens Brejner updated JENKINS-14746 Use nothing to build (grey builds) if there is no new baselines, our case 6843 Change By: Jens Brejner (19/Feb/13 8:55 AM) Summary: Use nothing to build (grey builds) if there is no new baselines, our case 8676 6843 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16872) Make the Mask Passwords Plugin work with Jenkins Promoted Builds plugin console
Tom Fanning created JENKINS-16872 Make the Mask Passwords Plugin work with Jenkins Promoted Builds plugin console Issue Type: Improvement Affects Versions: current Assignee: Daniel Petisme Components: mask-passwords, promoted-builds Created: 19/Feb/13 9:35 AM Description: The Mask Passwords plugin works perfectly for the main build console. However, it does not appear to work for the build console displayed and logged during build promotion. The Promoted Builds plugin is often used for deploying builds to remote servers, which often requires various forms of authentication on the command line. It would be very helpful for this plugin to handle this case. Project: Jenkins Priority: Major Reporter: Tom Fanning This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-10466) repository from jenkins main menu shows plain html codes
evernat commented on JENKINS-10466 repository from jenkins main menu shows plain html codes I think that this is may be fixed in version 0.9 of the plugin, by this commit: https://github.com/magnayn/Jenkins-Repository/commit/a1689d40587ff01d72c690549ffb81285f6b966e Is this issue reproduced with a recent version of the plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11920) All jobs (even a job with no steps) hang for twenty minutes after completion on Solaris
evernat commented on JENKINS-11920 All jobs (even a job with no steps) hang for twenty minutes after completion on Solaris 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-16873) Root workspace directory is removed when doing initial clone
Roman Prots' created JENKINS-16873 Root workspace directory is removed when doing initial clone Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 19/Feb/13 9:41 AM Description: When using GIT SCM the checkout of sources tries to delete root workspace directory. It can be "/usr/share/path-to-app" in my case. Jenkins user is not allowed to delete this directory. So build fails. Can we somehow don't remove the root workspace directory? Have not seen such problem with Subversion SCM. Project: Jenkins Priority: Major Reporter: Roman Prots' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-15025) Maven-Tycho 0.15.0 build - no additional info in console log about compilation failure
Andreas Bellmann commented on JENKINS-15025 Maven-Tycho 0.15.0 build - no additional info in console log about compilation failure Hi everyone. I need this bug/feature so much that I'm willing to pay 10.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/193/maven-tycho-0150-build-no-additional-info-in-console-log-about-compilation-failure). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16874) java.lang.NullPointerException: Current Project is null
Riccardo Gorza created JENKINS-16874 java.lang.NullPointerException: Current Project is null Issue Type: Bug Assignee: ragesh_nair Components: rebuild Created: 19/Feb/13 10:43 AM Description: Restarting Tomcat. During the restart process Jenkins fails to load jobs which use the "FSTrigger", if the rebuild-plugin is installed: Feb 18, 2013 1:01:45 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Eval-Hot-Systemtest java.lang.NullPointerException: Current Project is null at com.sonyericsson.rebuild.RebuildAction.getProject(RebuildAction.java:138) at com.sonyericsson.rebuild.RebuildAction.isRebuildAvailable(RebuildAction.java:276) at com.sonyericsson.rebuild.RebuildAction.getUrlName(RebuildAction.java:163) at org.jenkinsci.lib.envinject.service.EnvInjectActionRetriever.getEnvInjectAction(EnvInjectActionRetriever.java:36) at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getEnVars(EnvVarsResolver.java:54) at org.jenkinsci.lib.envinject.service.EnvVarsResolver.getPollingEnvVars(EnvVarsResolver.java:36) at org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger.start(FolderContentTrigger.java:371) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:97) at org.jenkinsci.lib.xtrigger.AbstractTrigger.start(AbstractTrigger.java:26) at hudson.model.AbstractProject.onLoad(AbstractProject.java:294) at hudson.model.Project.onLoad(Project.java:83) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2539) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java: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:722) => Rebuild plugin embeds the envinject library. There is a bug in the current version used by the rebuild plugin. Please upgrade to envinject-lib 1.16. => https://issues.jenkins-ci.org/browse/JENKINS-16809 Environment: Jenkins 1.502, latest plugins Project: Jenkins Labels: plugin, jenkins, rebuild envinject Priority: Major Reporter: Riccardo Gorza This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16809) Plugins FSTrigger/Envinject, NPE while loading jobs
Riccardo Gorza commented on JENKINS-16809 Plugins FSTrigger/Envinject, NPE while loading jobs Done: https://issues.jenkins-ci.org/browse/JENKINS-16874 Thanks + cheers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16875) Builds do not timeout when job hangs in post build actions
Dave Hunt created JENKINS-16875 Builds do not timeout when job hangs in post build actions Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: build-timeout Created: 19/Feb/13 10:47 AM Description: We're currently suffering from JENKINS-7641 where jobs hang when archiving artifacts on slaves. In this situation, the build timeout plugin does not timeout the build after the threshold has been reached. The jobs have to be aborted manually. Project: Jenkins Priority: Major Reporter: Dave Hunt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16875) Builds do not timeout when job hangs in post build actions
Dave Hunt commented on JENKINS-16875 Builds do not timeout when job hangs in post build actions This may be related to JENKINS-9716, which is about timing out during pre-build steps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16698) immediately update and show the result of one test case when it completed
Yinghua Wang updated JENKINS-16698 immediately update and show the result of one test case when it completed Change By: Yinghua Wang (19/Feb/13 10:51 AM) Labels: gui plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16523) Git plugin fails with NullPointerException (Error trying to determine the git version: Error performing command: --version)
YC Lian commented on JENKINS-16523 Git plugin fails with NullPointerException (Error trying to determine the git version: Error performing command: --version) Am having the same problem. There're 2 matters here: 1. It shouldn't be labeled as "Git installation directory" but "Git executable" 2. Not going to "Advanced" to "Save" will not enable the workaround - damn! Thanks Martin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16698) immediately update and show the result of one test case when it completed
Yinghua Wang commented on JENKINS-16698 immediately update and show the result of one test case when it completed Hi Bruno, I read the https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes and understood why in your current implementation the "Status" page or the "TestLink Action" page doesn't shows the runtime result result until iterated all the test cases. It seems that you call addAction() to attach the final test report to the build, it is called "Persistent actions". So it is available after all the test cases completed. To adopt my proposal, it seems that it is needed to add TransientBuildActionFactory to create the temporary action in order to update the test report. I have questions that when the transient action to be renewed or updated, and how to use TransientBuildActionFactory to reach it? What's your comment? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16876) Add support for virtual streams
Mikko Tapaninen created JENKINS-16876 Add support for virtual streams Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 19/Feb/13 11:09 AM Description: Perforce server 2012.1 introduced a new feature: virtual streams. These are logical constructs without depot paths, but can be used like real streams. Currently perforce plugin throws an exception when using a virtual stream: Caught exception communicating with perforce.com.tek42.perforce.PerforceException?: Stream 'foo/bar' doesn't exist. For Command: C:\apps\perforce\p4.exe -v 1 -P 0FA53FA932DFCE7659B95EFCCFA419A6 -s client -S foo/bar -i foo/bar is existing, but is virtual stream. Project: Jenkins Priority: Major Reporter: Mikko Tapaninen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16828) NullPointerException in BooleanSlice.get
James Howe commented on JENKINS-16828 NullPointerException in BooleanSlice.get Appears to only occur when slicing by view. Using the slicer on all projects works correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-7666) ClassCastException parsing JUnit result
YC Lian commented on JENKINS-7666 ClassCastException parsing JUnit result I just bumped into this too. I don't have Findbugs enabled, and running the build outside of Jenkins won't have this issue (just to differentiate). Am on 1.502, the latest, and perhaps I will build with Maven 3 (this is a Maven 2 project). $ ~/tools/hudson.tasks.Maven_MavenInstallation/Maven_2/bin/mvn clean install ... [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 50 seconds [INFO] Finished at: Tue Feb 19 19:33:31 MYT 2013 [INFO] Final Memory: 102M/244M [INFO] vs. at hudson.tasks.junit.TestResult.parse(TestResult.java:284) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:223) at hudson.tasks.junit.TestResult.parse(TestResult.java:192) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:148) at hudson.maven.Maven2Builder.postExecute(Maven2Builder.java:157) at hudson.maven.MavenBuilder$Adapter.postExecute(MavenBuilder.java:334) at hudson.maven.agent.PluginManagerInterceptor$1MojoIntercepterImpl.callPost(PluginManagerInterceptor.java:170) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:183) ... 34 more Caused by: org.dom4j.DocumentException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory Nested exception: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory at org.dom4j.io.SAXReader.read(SAXReader.java:484) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:129) at hudson.tasks.junit.TestResult.parse(TestResult.java:267) ... 41 more Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:97) at org.dom4j.io.SAXReader.getDocumentFactory(SAXReader.java:645) at org.dom4j.io.SAXReader.createContentHandler(SAXReader.java:969) at org.dom4j.io.SAXReader.read(SAXReader.java:449) ... 44 more [INFO] [INFO] Total time: 52 seconds [INFO] Finished at: Tue Feb 19 19:22:14 MYT 2013 [INFO] Final Memory: 100M/239M [INFO] Waiting for Jenkins to finish collecting data This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16449) When a job hits 'Max # of builds to keep' Nunit Publisher starts to throw NPE
gitt commented on JENKINS-16449 When a job hits 'Max # of builds to keep' Nunit Publisher starts to throw NPE We are getting the same exception in case of publishing JUnit results. But in our case "Max # of builds to keep" is not set. Builds which throw this exception are run on Windows slaves. As soon as we switched for these jobs from xUnit plug-in to standard "Publish JUnit test result report" the problem disappeared. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
andreas f created JENKINS-16877 In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Feb/13 12:25 PM Description: I'm extracting the latest build number of a job in a brute force way. Jobs using this functionality are failing after upgrading Jenkins from version 1.480.2 to 1.480.3. My problem occurs specifically when I use the XML API (https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API) and XPath expressions containing the function text(). Compare the following request: Request 1) $HUDSON_URL/job/$JOB_NAME/api/xml?xpath=//concurrentBuild/ Response 1) false w Request 2) $HUDSON_URL/job/$JOB_NAME/api/xml?xpath=//concurrentBuild/text() Response 2) The latter yields 403 Forbidden with no result when i try to fetch response with wget: [user@host ~]$ wget $HUDSON_URL/job/$JOB_NAME/api/xml?xpath=//concurrentBuild/text%28%29 -O wgetresponse -2013-02-19 12:54:23- $HUDSON_URL/job/$JOB_NAME/api/xml?xpath=//concurrentBuild/text%28%29 Resolving Connecting to ||... connected. HTTP request sent, awaiting response... 403 Forbidden 2013-02-19 12:54:23 ERROR 403: Forbidden. [user@host ~]$ ls -s wgetresponse 0 wgetresponse The output file is empty. The problem occurs for the request $HUDSON_URL/job/$JOB_NAME/api/xml?xpath=sum(//build/number) When I append &wrapper=list a java.lang.ClassCastException: java.lang.Double cannot be cast to org.dom4j.Node occurs. On the other hand, when text() is used inside the contains()-function, a correct response is given. $HUDSON_URL/job/$JOB_NAME/api/xml?xpath=//concurrentBuild[contains%28text%28%29,%27false%27%29] Environment: Windows XP, Jenkins v 1.480.3 (Long Term Support) Project: Jenkins Priority: Major Reporter: andreas f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16449) When a job hits 'Max # of builds to keep' Nunit Publisher starts to throw NPE
gitt edited a comment on JENKINS-16449 When a job hits 'Max # of builds to keep' Nunit Publisher starts to throw NPE We are getting the same exception in case of publishing JUnit results. But in our case "Max # of builds to keep" is not set. Builds which throw this exception are run on Windows slaves. As soon as we switched for these jobs from xUnit plug-in to standard "Publish JUnit test result report" the problem disappeared. Jenkins ver. 1.501 xUnit plug-in ver. 1.52 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16851) Strategy GerritTrigger missing with git plugin 1.1.28
rsandell commented on JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 Yes that looks very similar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-7666) ClassCastException parsing JUnit result
David Vonka commented on JENKINS-7666 ClassCastException parsing JUnit result no Findbugs here either, I'm on the same version as YC Lian. I get [INFO] Unable to execute mojo Embedded error: Failed to read //daily.semantacorp.com:8080/job/CE%20build/ws/semanta/target/surefire-reports/TEST-com.adaptavist.confluence.stats.StatsUtilTest.xml> org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory but when running maven as jenkins user from jenkins workspace from linux command line, everuthing is 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-9740) Access to static content is denied when jenkins works in private mode (anonymous access is disabled)
evernat commented on JENKINS-9740 Access to static content is denied when jenkins works in private mode (anonymous access is disabled) Access jnlp: this is intentional if I understood well. See JENKINS-16273, for example. All others: are they 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-16701) As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request
Manuel de la Peña resolved JENKINS-16701 as Fixed As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request Fixed in version 1.5 Change By: Manuel de la Peña (19/Feb/13 1:13 PM) Status: In Progress 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-7984) notifyCommit holds changes for about an hour after Hudson restart
evernat resolved JENKINS-7984 as Cannot Reproduce notifyCommit holds changes for about an hour after Hudson restart This is no longer an issue, as said by the reporter. Change By: evernat (19/Feb/13 1:18 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-9869) Jenkins Maven Release Plug-in fails because workspace directory does not exist
evernat resolved JENKINS-9869 as Incomplete Jenkins Maven Release Plug-in fails because workspace directory does not exist No response from the reporter, so resolving as incomplete. Please reopen if needed. Change By: evernat (19/Feb/13 1:17 PM) 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-10466) repository from jenkins main menu shows plain html codes
cforce commented on JENKINS-10466 repository from jenkins main menu shows plain html codes Looks good now. Found another error instead ;/ Will report issue 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-12843) Failure with maven 3 jobs and shade plugin
evernat commented on JENKINS-12843 Failure with maven 3 jobs and shade plugin 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-16878) UnsupportedOperationException at java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1012)
cforce created JENKINS-16878 UnsupportedOperationException at java.util.Collections$UnmodifiableCollection$1.remove(Collections.java:1012) Issue Type: Bug Assignee: magnayn Components: repository Created: 19/Feb/13 1:22 PM Description: Browsing to a url https://jenkins.loc/jenkins/plugin/repository/project/myproject/Build/ following Error! Build Status Code: 500 Exception: java.lang.RuntimeException: com.nirima.jenkins.webdav.interfaces.MethodException: Exception Stacktrace: javax.servlet.ServletException: java.lang.RuntimeException: com.nirima.jenkins.webdav.interfaces.MethodException: Exception at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:36) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:32) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextInt
[JIRA] (JENKINS-15874) Add the url to the build in the status message
Phil Rumble commented on JENKINS-15874 Add the url to the build in the status message Attempting a release 1.23 to handle 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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Note, after debugging: The issue that I faced: Had activation.jar in another webapp on same tomcat I learnt that(just now) tomcat uses common class loader. Hence it loaded both in to classpath/memory and created all this fuss I have undeployed the other application for now, jenkins is properly able to send email This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-15874) Add the url to the build in the status message
Phil Rumble started work on JENKINS-15874 Add the url to the build in the status message Change By: Phil Rumble (19/Feb/13 1:22 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 If anyone has any idea what has happened. Please do share 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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni edited a comment on JENKINS-16746 Unable to send email since Jenkins 1.500 Note, after debugging: The issue that I faced: Had activation.jar in another webapp on same tomcat I learnt that(just now) tomcat uses common class loader(might be wrong). Hence it loaded both in to classpath/memory and created all this fuss I have undeployed the other application for now, jenkins is properly able to send email This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16879) More robust display detection needed - builds fail when many builds require Xvnc
David Pärsson created JENKINS-16879 More robust display detection needed - builds fail when many builds require Xvnc Issue Type: Bug Assignee: Unassigned Components: xvnc Created: 19/Feb/13 2:23 PM Description: We're having issues with failing builds. We're running several builds in parallel on the same Jenkins machine, and many of them use XVNC, and I'm assuming it's related to this. Builds fail several times a day with the following error (though displays might differ, obviously): Starting xvnc [my-build] $ /usr/bin/vncserver :37 -geometry 1920x1280 A VNC server is already running as :37 Starting xvnc [my-build] $ /usr/bin/vncserver :49 -geometry 1920x1280 A VNC server is already running as :49 Starting xvnc [my-build] $ /usr/bin/vncserver :50 -geometry 1920x1280 A VNC server is already running as :50 Starting xvnc [my-build] $ /usr/bin/vncserver :51 -geometry 1920x1280 A VNC server is already running as :51 FATAL: Failed to run '/usr/bin/vncserver :51 -geometry 1920x1280' (exit code 98), blacklisting display #51; consider checking the "Clean up before start" option java.io.IOException: Failed to run '/usr/bin/vncserver :51 -geometry 1920x1280' (exit code 98), blacklisting display #51; consider checking the "Clean up before start" option at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:100) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:98) at hudson.plugins.xvnc.Xvnc.setUp(Xvnc.java:73) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1557) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) To me it seems like displays in use are blacklisted, and this is undesired since we currently don't have any stale locks in /tmp/.X11-unix/ (where our VNC locks are placed). Could locks in /tmp/.X*-lock and /tmp/.X11-unix/X* be considered when trying to start a new display? Could we allow more retries than the current 3? Or do you have any other ideas on how to address this issue? Environment: Ubuntu 12.04, Jenkins 1.500, XVNC plugin 1.10 Project: Jenkins Priority: Major Reporter: David Pärsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16851) Strategy GerritTrigger missing with git plugin 1.1.28
SCM/JIRA link daemon commented on JENKINS-16851 Strategy GerritTrigger missing with git plugin 1.1.28 Code changed in jenkins User: rsandell Path: gerrithudsontrigger/pom.xml gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerBuildChooser.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/65271af7819f62d258ec1cadd70434129bf299c9 Log: Fix For JENKINS-16851 It is probably fixed in git plugin v. 1.1.29 this commit should remove any use of deprecated APIs. But when I test this I gen something very similar to JENKINS-16849 at the end of the build. – 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-16849) StackOverflowError involving findMailAddressFor
SCM/JIRA link daemon commented on JENKINS-16849 StackOverflowError involving findMailAddressFor Code changed in jenkins User: rsandell Path: gerrithudsontrigger/pom.xml gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerBuildChooser.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/65271af7819f62d258ec1cadd70434129bf299c9 Log: Fix For JENKINS-16851 It is probably fixed in git plugin v. 1.1.29 this commit should remove any use of deprecated APIs. But when I test this I gen something very similar to JENKINS-16849 at the end of the build. – 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-10709) multiple builds are triggered for one change in Gerrit
Henrik Nilsson commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit same problem seen on: Jenkins 1.480.2 Gerrit Trigger 2.7.0 but now we even have triple builds, one with build number x and two with build number x+1. Is there anything we can help with to locate the 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-16865) SVN fail to revert working dir : NullPointerException
David Pärsson commented on JENKINS-16865 SVN fail to revert working dir : NullPointerException Are you trying to revert builds built on a slave? If so, this is currently not supported. Pull requests are welcome. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16865) SVN fail to revert working dir : NullPointerException
David Pärsson edited a comment on JENKINS-16865 SVN fail to revert working dir : NullPointerException Are you trying to revert builds built on a slave? If so, this is currently not supported. Reverting is only supported on the master at the moment. Pull requests are welcome. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16879) More robust display detection needed - builds fail when many builds require Xvnc
David Pärsson commented on JENKINS-16879 More robust display detection needed - builds fail when many builds require Xvnc If necessary I could contribute with a patch, but if so I'd appreciate if you could point me in a good direction. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16880) Provide more information for which plugins are causing error messages
kevin ran created JENKINS-16880 Provide more information for which plugins are causing error messages Issue Type: Improvement Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2013-02-19 at 9.51.09 AM.png Components: plugin Created: 19/Feb/13 2:54 PM Description: See screenshot. I think that I know which plugin is causing this error. It would be more helpful if I knew which plugin was causing this error though. Not sure if this is possible as it's talking about a GET vs POST link Project: Jenkins Priority: Minor Reporter: kevin ran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9701) Non-informative error message causing build faailure.
Michael Wright commented on JENKINS-9701 Non-informative error message causing build faailure. I'm seeing the same issue when attempting to convert from Check via XSLT. I have the following error messages: [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing Custom Tool [xUnit] [INFO] - [Custom Tool] - 18 test report file(s) were found with the pattern '*/check/*.xml' relative to '/var/lib/jenkins/jobs/impbus_unit_tests/workspace' for the testing framework 'Custom Tool'. [xUnit] [ERROR] - Conversion error Error to convert - A file not found ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception hudson.util.IOException2: There are some problems during the conversion into JUnit reports: at com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:164) at com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:37) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:171) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:116) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733) at hudson.model.Run.execute(Run.java:1593) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: com.thalesgroup.hudson.plugins.xunit.exception.XUnitException: Conversion error Error to convert - A file not found at com.thalesgroup.hudson.plugins.xunit.service.XUnitConversionService.convert(XUnitConversionService.java:89) at com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:135) ... 15 more Caused by: com.thalesgroup.dtkit.util.converter.ConversionException: Error to convert - A file not found at com.thalesgroup.dtkit.util.converter.ConversionService.convert(ConversionService.java:358) at com.thalesgroup.dtkit.util.converter.ConversionService.convert(ConversionService.java:172) at com.thalesgroup.dtkit.util.converter.ConversionService.convert(ConversionService.java:111) at com.thalesgroup.dtkit.metrics.model.InputMetricXSL.convert(InputMetricXSL.java:196) at com.thalesgroup.dtkit.metrics.model.InputMetricXSL.convert(InputMetricXSL.java:202) at com.thalesgroup.hudson.plugins.xunit.service.XUnitConversionService.convertCustomInputMetric(XUnitConversionService.java:104) at com.thalesgroup.hudson.plugins.xunit.service.XUnitConversionService.convert(XUnitConversionService.java:78) ... 16 more Caused by: org.xml.sax.SAXParseException; lineNumber: 70; columnNumber: 1; XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:253) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:288) at com.thalesgroup.dtkit.util.converter.ConversionService.convert(ConversionService.java:316) ... 22 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7666) ClassCastException parsing JUnit result
David Vonka commented on JENKINS-7666 ClassCastException parsing JUnit result The guide here: http://www.beyondlinux.com/2011/04/20/running-sonar-in-jenkinshudson-org-dom4j-documentfactory-cannot-be-cast-to-org-dom4j-documentfactory/ fixed the issue for me. Still, this is a bug, the guide is just a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16849) StackOverflowError involving findMailAddressFor
Artur Bańkowski commented on JENKINS-16849 StackOverflowError involving findMailAddressFor I'v upgraded to git plugin to 1.1.29 but I have still similar problem: http://pastebin.com/T0CAh1bB Jenkins 1.502 Linux frisco-builder 2.6.32-5-xen-amd64 #1 SMP Fri Sep 9 22:23:19 UTC 2011 x86_64 GNU/Linux Debian Squeeze This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16865) SVN fail to revert working dir : NullPointerException
kutzi updated JENKINS-16865 SVN fail to revert working dir : NullPointerException assigning to right component subversion Change By: kutzi (19/Feb/13 3:44 PM) Component/s: subversion Component/s: svn-release-mgr Component/s: svn-revert-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9701) Non-informative error message causing build faailure.
Michael Wright commented on JENKINS-9701 Non-informative error message causing build faailure. A little more color here: The error was a result of an XML file being malformed. However, the issue still stands that the error message is patently unhelpful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16881) Missing XML Declaration in Node's config.xml
cynipe
created JENKINS-16881
Missing XML Declaration in Node's config.xml
Issue Type:
Bug
Assignee:
cynipe
Components:
core
Created:
19/Feb/13 3:58 PM
Description:
$ curl http://localhost:8080/computer/%28master%29/config.xml
1.0
2
NORMAL
true
"hudson.security.AuthorizationStrategy$Unsecured"/>
"hudson.security.SecurityRealm$None"/>
"jenkins.model.ProjectNamingStrategy$DefaultProjectNamingStrategy"/>
${ITEM_ROOTDIR}/workspace
${ITEM_ROOTDIR}/builds
"hudson.views.DefaultViewsTabBar"/>
"hudson.views.DefaultMyViewsTabBar"/>
test
1
NORMAL
"hudson.slaves.RetentionStrategy$Always"/>
"hudson.slaves.JNLPLauncher"/>
anonymous
0
"hudson" reference="../../.."/>
すべて
false
false
"hudson.model.View$PropertyList"/>
すべて
0
This happens since https://github.com/cynipe/jenkins/commit/660c0f6e61b2616da93ffb82009d5e6ad9c29c23 is released.
Project:
Jenkins
Labels:
api
node
slave
Priority:
Major
Reporter:
cynipe
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 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-16881) Missing XML Declaration in Node's config.xml
cynipe commented on JENKINS-16881 Missing XML Declaration in Node's config.xml https://github.com/jenkinsci/jenkins/pull/715 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16881) Missing XML Declaration in Node's config.xml
cynipe commented on JENKINS-16881 Missing XML Declaration in Node's config.xml https://github.com/cynipe/jenkins/commit/5711dedc11a7d742ca3daa7c79cc76c5a580a3da This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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
Richard Merrill commented on JENKINS-15156 Builds disappear from build history after completion Hard to tell if this fix made it in to 1.502 since they forgot to update the changelog. :/ The Build History timeline graphical display still isn't showing all of the builds, so maybe that'll have to be written up as a separate bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16881) Missing XML Declaration in Node's config.xml
cynipe
updated JENKINS-16881
Missing XML Declaration in Node's config.xml
Change By:
cynipe
(19/Feb/13 4:19 PM)
Description:
{code}$ curl http://localhost:8080/computer/%28master%29/config.xml1.0 2 NORMAL true${ITEM_ROOTDIR}/workspace ${ITEM_ROOTDIR}/buildstest 1 NORMAL anonymous0 すべて false false すべて 0 {code}This happens since https://github.com/
cynipe
jenkinsci
/jenkins/commit/660c0f6e61b2616da93ffb82009d5e6ad9c29c23 is released.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 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-16865) SVN fail to revert working dir : NullPointerException
David Pärsson edited a comment on JENKINS-16865 SVN fail to revert working dir : NullPointerException Are you trying to revert builds built on a slave? If so, this is currently not supported. Reverting is only supported on the master at the moment. Pull requests are welcome. This is not related to the svn-revert-plugin, as kutzi states. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16865) SVN fail to revert working dir : NullPointerException
David Pärsson updated JENKINS-16865 SVN fail to revert working dir : NullPointerException Change By: David Pärsson (19/Feb/13 4:25 PM) Assignee: David Pärsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-14144) Build config history getting spammed
Zoltán Buza commented on JENKINS-14144 Build config history getting spammed I also don't see the point why EnvInject has to modify job config before and after each build. Can someone explain it in details? I would really appreciate that! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16865) SVN fail to revert working dir : NullPointerException
Emmanuel Boudrant commented on JENKINS-16865 SVN fail to revert working dir : NullPointerException Yes, my mistake, I looked for a component starting by svn* ... not sub* 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-16882) Job-B ${WORKSPACE} has value of Job-A WORKSPACE
Riccardo Gorza
created JENKINS-16882
Job-B ${WORKSPACE} has value of Job-A WORKSPACE
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
envinject, fstrigger
Created:
19/Feb/13 5:07 PM
Description:
If Jenkins job "A" has a configured fstrigger-trigger, then some other Jenkins jobs "B" (not all) will inherit the job "A" value for their ${WORKSPACE} env-variable. Keeping job "A", but removing the fstrigger and restarting Jenkins, will solve the issue. Adding an explicit WORKSPACE to all "B"-jobs will solve the issue. Job "A" does not directly use the envinject plugin, but "B" jobs do.
Environment:
Jenkins 1.502, fstrigger 0.35, envinject 1.83
Project:
Jenkins
Priority:
Major
Reporter:
Riccardo Gorza
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 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
Richard Mortimer commented on JENKINS-15156 Builds disappear from build history after completion The fixes made it into the 1.502 release. Its listed in the changelog (lines 67 & 68) https://github.com/jenkinsci/jenkins/blob/5bca85d99253a85ae6085fc38ac592d97d8e98e6/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-14699) hg clone adding "@2" to end of clone destination path
mat007 commented on JENKINS-14699 hg clone adding "@2" to end of clone destination path We're using SVN and very regularly (e.g. once a week) we experience this issue. Sometimes it even goes to @3 or @4 before we notice. The thing is the workspace does exist, it just seems for some reason something decides to switch to the @2 workspace. For instance one build starts with : Started by an SCM change Building remotely on Slave-2 in workspace E:\workspace\ Updating http://svn.///trunk at revision '2013-02-19T15:26:09.965 +0100' and the next one : Started by an SCM change Building remotely on Slave-2 in workspace E:\workspace\@2 Checking out a fresh workspace because E:\workspace\@2\trunk doesn't exist Cleaning local Directory trunk Checking out http://svn.///trunk at revision '2013-02-19T17:11:09.863 +0100' We are using matrix builds with a few slaves started via jnlp, all on windows. Any clue how we could help debug this ? It is quite inconvenient as some of our projects take up to 70GB disk space and duplicating them fills up the disk pretty quickly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16883) Doxygen plugin can't find output directory.
Kevin Moran
created JENKINS-16883
Doxygen plugin can't find output directory.
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
doxygen
Created:
19/Feb/13 6:34 PM
Description:
I can't get jenkins to build and publish with the doxygen plugin. I get the error below:
find . -name *.m -exec grep -i -H XXX '{}' \;
Archiving artifacts
Publishing Doxygen HTML results.
FATAL: error
hudson.AbortException: The output directory doesn't exist.
at hudson.plugins.doxygen.DoxygenDirectoryParser.retrieveDoxygenDirectoryFromDoxyfile(DoxygenDirectoryParser.java:354)
at hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:53)
at hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:14)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Thread.java:680)
Build step 'Publish Doxygen' changed build result to FAILURE
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE
The output directory is the directory where my Doxyfile is.
I have doxygen installed on my build machine under /usr/local/bin/doxygen.
My output dir is: OUTPUT_DIRECTORY = myProj/docs/
My doxyfile is: myProj/docs/Doxyfile
I've searched and this error seems common, but it looks like it's supposedly fixed in v0.11 which is what I'm running.
Environment:
Mac
Project:
Jenkins
Priority:
Major
Reporter:
Kevin Moran
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 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-16849) StackOverflowError involving findMailAddressFor
Michael Clarke commented on JENKINS-16849 StackOverflowError involving findMailAddressFor The stack trace given above has nothing to do with the CVS plugin - it's being caused by mailer trying to retrieve a user's address which uses the Git mail address resolver which checks the Git changeset to see if a user in involved in that change which checks a user property to see if their address is set which tries to retrieve the user. On a side note, the CVS mail address resolver has been removed from the CVS plugin as of today's release (2.8) so any related issue in the CVS plugin will no longer appear. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16849) StackOverflowError involving findMailAddressFor
Michael Clarke updated JENKINS-16849 StackOverflowError involving findMailAddressFor Change By: Michael Clarke (19/Feb/13 6:49 PM) Component/s: cvs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16325) TAP Parser can't handle the output from prove
Jochen Koegel commented on JENKINS-16325 TAP Parser can't handle the output from prove You can can use prove's --archive parameter to put one tap-file per test script into a directory: prove *.t --archive tap/ works nicely with jenkins + tap4j in my setup. Does this solve your 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-16883) Doxygen plugin can't find output directory.
Kevin Moran resolved JENKINS-16883 as Not A Defect Doxygen plugin can't find output directory. Didn't know I needed to add a build command explicitly running doxygen. Should put a readme with the code saying that. Change By: Kevin Moran (19/Feb/13 7:35 PM) Status: Open Resolved Resolution: 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-15135) Support for "Poll on Master" for Subversion SCM plugin
Michael Clarke commented on JENKINS-15135 Support for "Poll on Master" for Subversion SCM plugin The code in the plugin does work. You need to set an environment variable, possible using one of the following methods: 1. If you're using 'java -jar jenkins.war' to run jenkins then change your command to be 'java -Dhudson.scm.SubversionSCM.pollFromMaster=true -jar jenkins.war' 2. Run 'set hudson.scm.SubversionSCM.pollFromMaster=true' (Windows) or 'export hudson.scm.SubversionSCM.pollFromMaster=true' (Unix) in your command shell before running 'java -jar jenkins.war' (or launching any container from that shell) 2. Add an entry to the Windows environment variables of 'hudson.scm.SubversionSCM.pollFromMaster' with the value of 'true', or add it to your shell environment if you're on Unix/Linux environment to allow the variable to be picked up between restarts without manual intervention (this only needs done on the master AFAIK) 3. If you're running Jenkins in a container then search for how to set environment variables in that container, you'll need something like the following if you're using Tomcat: There's a general aversion to adding additional checkboxes to the config screens since they're pretty full already, although I don't know if this is was you're looking for. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-4895) AD and LDAP fail due to Referrals
Casey McGinty commented on JENKINS-4895 AD and LDAP fail due to Referrals This bug causes the following exception: org.acegisecurity.AuthenticationServiceException: LdapCallback;null; nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: example.com:389 [Root exception is java.net.ConnectException: Connection refused: connect]]; nested exception is org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;null; nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: example.com:389 [Root exception is java.net.ConnectException: Connection refused: connect]] It appears that Jenkins still throws an exception when 'Context.REFERRAL' is set to 'ignore'. org.acegisecurity.AuthenticationServiceException: LdapCallback;Unprocessed Continuation Reference(s); nested exception is javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name ''; nested exception is org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;Unprocessed Continuation Reference(s); nested exception is javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name '' If you set your root DN one level deep, like "OU=Site,DC=example,DC=com" then it will work correctly. This doesn't work if you need to validate from the root level. I think the correct fix is to: a) do not throw an exception if the referral connection is refused, just log it as a warning b) if Context.REFERRAL is 'ignore', do not follow referrals or throw an exception when referral is hit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16810) CLI: java.io.EOFException
Paul Landolt commented on JENKINS-16810 CLI: java.io.EOFException Happening in 1.502 as well: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-15846) Deadlock during Maven builds Parsing POM step
Jesse Glick commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step "pool-635-thread-1" … BLOCKED on org.apache.maven.wagon.providers.http.commons.logging.impl.WeakHashtable@13cbe4 owned by "pool-635-thread-2" … at java.util.Hashtable.remove(Hashtable.java:435) - blocked on org.apache.maven.wagon.providers.http.commons.logging.impl.WeakHashtable@13cbe4 at org.apache.maven.wagon.providers.http.commons.logging.impl.WeakHashtable.purgeOne(WeakHashtable.java:338) - locked java.lang.ref.ReferenceQueue@1b8447f at org.apache.maven.wagon.providers.http.commons.logging.impl.WeakHashtable.put(WeakHashtable.java:238) at org.apache.maven.wagon.providers.http.commons.logging.LogFactory.cacheFactory(LogFactory.java:1004) "pool-635-thread-2" … BLOCKED on java.lang.ref.ReferenceQueue@1b8447f owned by "pool-635-thread-1" … at org.apache.maven.wagon.providers.http.commons.logging.impl.WeakHashtable.purge(WeakHashtable.java:323) - blocked on java.lang.ref.ReferenceQueue@1b8447f at org.apache.maven.wagon.providers.http.commons.logging.impl.WeakHashtable.rehash(WeakHashtable.java:312) at java.util.Hashtable.put(Hashtable.java:412) - locked org.apache.maven.wagon.providers.http.commons.logging.impl.WeakHashtable@13cbe4 at org.apache.maven.wagon.providers.http.commons.logging.impl.WeakHashtable.put(WeakHashtable.java:242) at org.apache.maven.wagon.providers.http.commons.logging.LogFactory.cacheFactory(LogFactory.java:1004) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16849) StackOverflowError involving findMailAddressFor
Nicolas De Loof commented on JENKINS-16849 StackOverflowError involving findMailAddressFor so, short term fix is to update cvs plugin. longer term fix is to stop creating jenkins User in a getter :-/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16746) Unable to send email since Jenkins 1.500
Alex Earl commented on JENKINS-16746 Unable to send email since Jenkins 1.500 You can enable is in jenkins.xml with the options to the JVM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16128) Broken Jenkins Configuration page when Github SQS plugin is installed
Mark Badolato commented on JENKINS-16128 Broken Jenkins Configuration page when Github SQS plugin is installed Seems to be working well now. 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-4895) AD and LDAP fail due to Referrals
Casey McGinty
commented on JENKINS-4895
AD and LDAP fail due to Referrals
Ok, I found another workaround. The issue is that the referral points to an invalid server. To fix this, all you have to do is edit your HOSTS file to point the DNS entry back to the LDAP server. In my situation I have Jenkins on a Windows box and the referral points to EXAMPLE.COM.
Edit C:\Windows\System32\drivers\etc\hosts, add the line:
XX.XX.XX.XXexample.com
where XX.XX.XX.XX is the IP address of your LDAP server.
Also, unrelated to this bug, but for completeness your LDAP 'User Search Filter' should probably be "SAMAccountName={0}" if you are using LDAP over Active Directory.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 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-15846) Deadlock during Maven builds Parsing POM step
Jesse Glick commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step Tricky because there is not yet a Commons Logging release including the fix, and the current version (1.1.1) is packed into wagon-http-2.3-shaded.jar. To fix, would need at least a beta of 1.1.2 to be released, and then for Wagon 2.5 or similar to be released, at which point Jenkins could pick it up in the Maven plugin. Or Jenkins would have to fork both Commons Logging and Wagon, which is not an appealing prospect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-4934) Plot data is retained for deleted builds
Michael Clarke commented on JENKINS-4934 Plot data is retained for deleted builds How do you see this working for builds that are auto-deleted by Jenkins as part of it's normal cleanup (e.g. if a user has set builds to only be retained for 5 days, or only the last 5 builds are to be kept)? Would you expect these removed build to be automatically removed from the plot too? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-10466) repository from jenkins main menu shows plain html codes
evernat resolved JENKINS-10466 as Cannot Reproduce repository from jenkins main menu shows plain html codes ok, thanks. You may of course create another issue. Change By: evernat (19/Feb/13 9:29 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-14970) XML File pattern for JSLINT is not getting persisted.
Darrell King commented on JENKINS-14970 XML File pattern for JSLINT is not getting persisted. I've created a pull request with a fix for this issue. https://github.com/jenkinsci/violations-plugin/pull/27 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16884) EC2 plugin starts too many slave nodes
Andrew Coulton created JENKINS-16884 EC2 plugin starts too many slave nodes Issue Type: Bug Assignee: Francis Upton Components: ec2, plugin Created: 19/Feb/13 10:02 PM Description: As soon as I queue a single build, the ec2 plugin spins up multiple ec2 build slaves at the same instant. My logs show: Feb 19, 2013 12:58:03 PM hudson.slaves.NodeProvisioner update INFO: www.edbookfest dev-server build slave (ami-089c957c) provisioning successfully completed. We have now 2 computer(s) Feb 19, 2013 12:57:54 PM hudson.slaves.NodeProvisioner update INFO: www.edbookfest dev-server build slave (ami-089c957c) provisioning successfully completed. We have now 2 computer(s) Feb 19, 2013 12:56:10 PM hudson.slaves.NodeProvisioner update INFO: Started provisioning www.edbookfest dev-server build slave (ami-089c957c) from ec2-eu-west-1 with 2 executors. Remaining excess workload:-3.0 Feb 19, 2013 12:56:10 PM hudson.slaves.NodeProvisioner update INFO: Started provisioning www.edbookfest dev-server build slave (ami-089c957c) from ec2-eu-west-1 with 2 executors. Remaining excess workload:-1.0 Feb 19, 2013 12:56:09 PM hudson.slaves.NodeProvisioner FINE: Excess workload 1.0 detected. (planned capacity=5.6E-45,Qlen=8.921825E-28,idle=2.4934977E-16&0,total=0m,=1.0) I think it only stops at two because of the instance cap, I have experienced it putting in more. I tried increasing the number of executors per instance to two in the hope that would make it realise it had capacity coming onstream but that hasn't made any difference, as you see above it goes immediately to -3.0 excess workload. I think this may be related to JENKINS-5334 and JENKINS-6691 but they seem both to involve slightly different circumstances either where additional builders are correctly required, or where there is a time delay in start up. Environment: Jenkins 1.499, Amazon EC2 plugin v1.17 Project: Jenkins Priority: Critical Reporter: Andrew Coulton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16884) EC2 plugin starts too many slave nodes
Francis Upton commented on JENKINS-16884 EC2 plugin starts too many slave nodes Hi Andrew, There has been much work on this problem and the current source of the plugin should have this fixed. We have not released this version yet. Are you in a position to build the plugin and try from from the current source? If not I can provide you with a Jar file in a day or so to try. And then soon we can release a new version with this fixed. Francis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-6415) invalid svn:externals warnings are swallowed silently and ignored during checkout
evernat commented on JENKINS-6415 invalid svn:externals warnings are swallowed silently and ignored during checkout Hi all, Is it reproduced with recent versions of the subversion plugin and of Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9142) "Add Build Step" button broken in job configure page
christer moren commented on JENKINS-9142 "Add Build Step" button broken in job configure page I got the same problem when trying to add portlets to the dashboard view in 1.501. Prepared to agree with Edward Griffin that it relates to the cookies. I had a lot of JSESSIONID. cookies, removing all of them seemed to solve the problem (so I guess it might have choosen the wrong one). Other than the broken link (404) I could not find any other errors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16884) EC2 plugin starts too many slave nodes
Andrew Coulton commented on JENKINS-16884 EC2 plugin starts too many slave nodes Hi Francis, Thanks for the very rapid response, and apologies for duplication. I'm not set up to build the plugin from source at the moment, so if you did have a jar file ahead of the next release that would be really helpful. Many thanks, Andrew This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16849) StackOverflowError involving findMailAddressFor
SCM/JIRA link daemon commented on JENKINS-16849 StackOverflowError involving findMailAddressFor Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitChangeSet.java http://jenkins-ci.org/commit/git-plugin/65c00213283c1e909a834467d9cd7a322e153594 Log: JENKINS-16849 disable isMailerPropertySet need to be able to check Mailer.UserProperty#address is set without invoking MailAddressResolver This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16849) StackOverflowError involving findMailAddressFor
kutzi commented on JENKINS-16849 StackOverflowError involving findMailAddressFor @mc1arke: it's not true that this has nothing to do with the cvs-plugin: at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21) This is in fact the mail address resolver of the cvs-plugin (see https://github.com/jenkinsci/cvs-mail-address-resolver-plugin/blob/master/src/main/java/hudson/scm/MailAddressResolverImpl.java). This is also in sync with the reports that disabling the csv-plugin works around this issue. You're right that this has been moved to a new plugin in the mean time, but at the time of reporting this was an issue with the git-plugin AND the cvs-plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16849) StackOverflowError involving findMailAddressFor
kutzi commented on JENKINS-16849 StackOverflowError involving findMailAddressFor @Nicolas: I agree that it's ridiculous that UserProperty.getAddress() triggers a whole lot of (often) expensive lookups This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16869) exception when trying to open Configuration Slicing "Timestamper Slicer"
Adam Sloan commented on JENKINS-16869 exception when trying to open Configuration Slicing "Timestamper Slicer" upgraded to Jenkins 1.502 and builds by timer working again, but still get this Configuration Slicing exception This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 edited a comment on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Propfile is not from email-ext, its from token-macro. Which means you would need to have someone fix it for that plugin too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16885) Expose variables for approving users
Alex Halovanic created JENKINS-16885 Expose variables for approving users Issue Type: Patch Affects Versions: current Assignee: Unassigned Components: promoted-builds Created: 20/Feb/13 3:30 AM Description: In the promoted builds plugin, it would be nice to expose information available about the users who manually approved it (for example, I send an email from the promotion script when it completes). I've attached a simple patch to do this. Project: Jenkins Labels: plugin Priority: Trivial Reporter: Alex Halovanic This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16860) Support for cloudformation CAPABILITIES option
edovale commented on JENKINS-16860 Support for cloudformation CAPABILITIES option Currently, we create all stacks passing the CAPABILITY_IAM value for capabilities to the stack creation API request. Sometimes when the first creation of a stach fails, the stack is rolled_back but not deleted. If this is the case then next request toc reate the stack will fail because of a name collision. Could this be what you are experiencing? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-13959) StackOverflowException on Job Finish
Ben Caradoc-Davies updated JENKINS-13959 StackOverflowException on Job Finish Change By: Ben Caradoc-Davies (20/Feb/13 5:02 AM) Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-13959) StackOverflowException on Job Finish
Ben Caradoc-Davies commented on JENKINS-13959 StackOverflowException on Job Finish I see this on Jenkins 1.502 even with CVS disabled; we are using mailer 1.5, git plugin 1.1.29, and a git-managed SCM. Here is a stacktrace excerpt: at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser.parse(MultiSCMChangeLogParser.java:140) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:932) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:906) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:453) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1554) at hudson.model.User.getProjects(User.java:448) at hudson.scm.BlameSubversionMailAddressResolverImpl.findMailAddressFor(BlameSubversionMailAddressResolverImpl.java:23) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:290) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:276) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:324) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:455) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1554) at hudson.model.User.getProjects(User.java:448) at hudson.scm.BlameSubversionMailAddressResolverImpl.findMailAddressFor(BlameSubversionMailAddressResolverImpl.java:23) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532) at hudson.plugins.git.GitChangeSet.isMailerPropertySet(GitChangeSet.java:290) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:276) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:324) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:455) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1554) at hudson.model.User.getProjects(User.java:448) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-13959) StackOverflowException on Job Finish
Ben Caradoc-Davies commented on JENKINS-13959 StackOverflowException on Job Finish I am seeing this failure even with email notification disabled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
