[JIRA] (JENKINS-16267) Support multiple report directories
Norman Seidel created JENKINS-16267 Support multiple report directories Issue Type: Improvement Affects Versions: current Assignee: Vaclav Tunka Components: tattletale Created: 07/Jan/13 11:28 AM Description: Unfortunately, maven tattletale plugin doesn't support a aggregation of its reports. So in a multi-module project you get a tattletale report for each module. But the tattletale-plugin for jenkins only looks in one directory and so in our case the tattletale link point to nowhere. So please either look recursive for the configured directory or make it possible to configure more than one report directory. Environment: Tattletale plugin 0.3 Project: Jenkins Priority: Major Reporter: Norman Seidel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16121) maven-soapui-plugin configurable outputFolder
Norman Seidel updated JENKINS-16121 maven-soapui-plugin configurable outputFolder Change By: Norman Seidel (13/Dec/12 3:59 PM) Description: There was a fix in JENKINS-11353 to recognize test results from eviware:maven-soapui-plugin. Currently SurefireArchiver looks in the plugin configuration if the Mojo is surefire or failsafe.But in maven-soapui-plugin you can configure "outputFolder" for your surefire-reports. We are running multiple executions of maven-soapui-plugin with different versions of the "same" testsuites (same testcases). If we want to keep all surefire-reports we have to configure multiple reports directories or "outputFolder" in the soapui-plugin. But Jenkins only looks for "target/surefire-reports" by default (non surefire oder failsafe plugin). So this doesn't work. And if all executions write to "target/surefire-reports" the they overwrite themselves.Aim: If the Mojo is maven-soapui-plugin the then look in the configuration for "outputFolder" as it is done for surefire and failsafe. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16121) maven-soapui-plugin configurable outputFolder
Norman Seidel updated JENKINS-16121 maven-soapui-plugin configurable outputFolder Change By: Norman Seidel (13/Dec/12 3:57 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16121) maven-soapui-plugin configurable outputFolder
Norman Seidel created JENKINS-16121 maven-soapui-plugin configurable outputFolder Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: maven Created: 13/Dec/12 3:56 PM Description: There was a fix in JENKINS-11353 to recognize test results from eviware:maven-soapui-plugin. Currently SurefireArchiver looks in the plugin configuration if the Mojo is surefire or failsafe. But in maven-soapui-plugin you can configure "outputFolder" for your surefire-reports. We are running multiple executions of maven-soapui-plugin with different versions of the "same" testsuites (same testcases). If we want to keep all surefire-reports we have to configure multiple reports directories or "outputFolder" in the soapui-plugin. But Jenkins only looks for "target/surefire-reports" by default (non surefire oder failsafe plugin). So this doesn't work. And if all executions write to "target/surefire-reports" the overwrite themselves. Aim: If the Mojo is maven-soapui-plugin the look in the configuration for "outputFolder" as it is done for surefire and failsafe. Environment: Linux, Jenkins 1.492, Java 1.6.0_33 Project: Jenkins Labels: maven testreport test Priority: Major Reporter: Norman Seidel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Norman Seidel commented on JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) I've got the same problem for Synergy CM and Jenkins 1.489. Jenkins 1.488 works fine. 07.11.2012 14:54:46 hudson.triggers.SCMTrigger$Runner runPolling SCHWERWIEGEND: Failed to record SCM polling for hudson.maven.MavenModuleSet@32c3601b[xxx-continuous_1.6.0] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1937) at hudson.Launcher.inherit(Launcher.java:1068) at hudson.Launcher.access$100(Launcher.java:80) at hudson.Launcher$LocalLauncher.launch(Launcher.java:756) at hudson.Launcher$2.launch(Launcher.java:723) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.Launcher$ProcStarter.join(Launcher.java:353) at hudson.plugins.synergy.impl.Commands.executeSynergyCommand(Commands.java:175) at hudson.plugins.synergy.util.SessionUtils.openSession(SessionUtils.java:87) at hudson.plugins.synergy.SynergySCM.pollChanges(SynergySCM.java:1062) at hudson.scm.SCM.poll(SCM.java:375) at hudson.model.AbstractProject._poll(AbstractProject.java:1471) at hudson.model.AbstractProject.poll(AbstractProject.java:1404) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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 java.lang.Thread.run(Thread.java:662) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12744) Execute a command before timeout
Norman Seidel commented on JENKINS-12744 Execute a command before timeout Exactly what we need / would like to have (thread dump). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
