[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 Sorry, Alex confused you with someone else .. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (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 Same with you 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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Hey alex try searching for find -iname *activation*.jar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 Yes, Alex. Our tomcat server had been recently deployed with another webapp which had a different version of activation.jar. I had undeployed this new application and everything is back to normal. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 You can add the same options in bin/catalina.sh under the first line as: #!... JAVA_OPTS=$JAVA_OPTS" -Dmail.debug=true" ...Some copyright info... (OR) #!... JAVA_OPTS=$JAVA_OPTS:"-Dmail.debug=true" ...Some copyright info... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (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-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 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-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni reopened JENKINS-16746 Unable to send email since Jenkins 1.500 In that case, lets just keep it open if someone wants to fix it. Change By: Ravi Teja Lokineni (12/Feb/13 12:31 PM) Resolution: Won't Fix Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Nothing was changed in the settings, everything was as-is since Jenkins 1.4xx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 created JENKINS-16746 Unable to send email since Jenkins 1.500 Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 11/Feb/13 7:04 AM Description: Note: The default 'test configuration email' sent mail successfully but after build finishes the plugin is not able to send mail Stacktrace: ERROR: Could not send email as a part of the post-build publishers. javax.mail.MessagingException: IOException while sending message; nested exception is: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="=_Part_34_1307232537.1360285420086" at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1141) at javax.mail.Transport.send0(Transport.java:195) at javax.mail.Transport.send(Transport.java:124) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:308) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="=_Part_34_1307232537.1360285420086" at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:877) at javax.activation.DataHandler.writeTo(DataHandler.java:302) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099) ... 13 more Project: Jenkins Priority: Critical Reporter: Ravi Teja Lokineni This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16159) Add a post-build action to generate war file
Ravi Teja Lokineni created JENKINS-16159 Add a post-build action to generate war file Issue Type: Bug Assignee: jeffg2one Components: grails Created: 18/Dec/12 1:34 PM Description: We cannot publish cobertura report and generate a clean war file in the pre-build steps. Since generating a clean war includes cleaning the test-reports and compiled class files and results in build failure with no test reports ready for publishing Project: Jenkins Priority: Major Reporter: Ravi Teja Lokineni This message is automatically generated by JIRA. 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-15678) Support for automatics issue diagnosis
Ravi Teja Lokineni created JENKINS-15678 Support for automatics issue diagnosis Issue Type: New Feature Assignee: Unassigned Components: core Created: 31/Oct/12 9:30 AM Description: Atlassian has this feature under the name Hercules. http://www.atlassian.com/hercules/ The idea is: Sniff for stacktraces, try to find suggested fixes Or Submit the stacktrace to developers with some environment details Environment: All Project: Jenkins Priority: Major Reporter: Ravi Teja Lokineni This message is automatically generated by JIRA. 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-15678) Support for automatic issue diagnosis/reporting
Ravi Teja Lokineni updated JENKINS-15678 Support for automatic issue diagnosis/reporting Change By: Ravi Teja Lokineni (31/Oct/12 9:31 AM) Summary: Support for automatic issue diagnosis /reporting This message is automatically generated by JIRA. 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-15678) Support for automatic issue diagnosis
Ravi Teja Lokineni updated JENKINS-15678 Support for automatic issue diagnosis Change By: Ravi Teja Lokineni (31/Oct/12 9:31 AM) Summary: Support for automatics automatic issue diagnosis This message is automatically generated by JIRA. 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Ravi Teja Lokineni commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Same is the case with me too: WARNING: could not load //jenkins_home/jobs/functional/builds/73 hudson.util.IOException2: Invalid directory name //jenkins_home/jobs/functional/builds/73 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:332) at hudson.model.Run.(Run.java:278) at hudson.model.AbstractBuild.(AbstractBuild.java:179) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor55.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1061) at hudson.model.AbstractProject$1.create(AbstractProject.java:275) at hudson.model.AbstractProject$1.create(AbstractProject.java:273) at hudson.model.RunMap.retrieve(RunMap.java:220) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:638) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:601) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:344) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:502) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:355) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:100) at hudson.model.RunMap$1.next(RunMap.java:107) at hudson.model.RunMap$1.next(RunMap.java:96) at hudson.widgets.HistoryWidget.getRenderList(HistoryWidget.java:131) at sun.reflect.GeneratedMethodAccessor220.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(Script
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Ravi Teja Lokineni updated JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Change By: Ravi Teja Lokineni (31/Oct/12 9:04 AM) Environment: win Server 2008 R2 - tomcat , CentOS Tomcat 6 Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Ravi Teja Lokineni
updated JENKINS-15587
Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Change By:
Ravi Teja Lokineni
(31/Oct/12 9:03 AM)
Description:
After updating to 1.485, I have the following error after jenkins loading.At the beginning, all builds are present, but as long as jenkins parse the builds directory one by one amd make the "Unparseable date" error, they are removed from the interface. After several minutes there are no more builds available in jobs.=> it seems jenkins tried to parse the directory name as the date ?
{noformat}
Oct 13, 2012 2:23:50 PM hudson.model.RunMap retrieveWARNING: could not load c:\.jenkins\jobs\SIM3-Test-3\builds\39hudson.util.IOException2: Invalid directory name c:\.jenkins\jobs\SIM3-Test-3\builds\39 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:332) at hudson.model.Run.(Run.java:278) at hudson.model.AbstractBuild.(AbstractBuild.java:182) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor110.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1061) at hudson.model.AbstractProject$1.create(AbstractProject.java:275) at hudson.model.AbstractProject$1.create(AbstractProject.java:273) at hudson.model.RunMap.retrieve(RunMap.java:217) at hudson.model.RunMap.retrieve(RunMap.java:58) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:596) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:566) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:334) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:467) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:345) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:210) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103) at hudson.model.Job.getBuildStabilityHealthReport(Job.java:945) at hudson.model.Job.getBuildHealthReports(Job.java:905) at hudson.model.Job.getBuildHealth(Job.java:870) at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
[JIRA] (JENKINS-13549) Duplicate test results are shown for grails projects
Ravi Teja Lokineni updated JENKINS-13549 Duplicate test results are shown for grails projects Change By: Ravi Teja Lokineni (03/Sep/12 12:21 PM) Summary: Duplicate test results are shown for grails projectsgr projects This message is automatically generated by JIRA. 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-13549) Duplicate test results are shown for grails projectsgr
Ravi Teja Lokineni commented on JENKINS-13549 Duplicate test results are shown for grails projectsgr It is working with 'target/test-reports/TEST-*.xml' This message is automatically generated by JIRA. 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-11025) Allow the build to fail on low coverage
Ravi Teja Lokineni commented on JENKINS-11025 Allow the build to fail on low coverage I've been waiting for this since a long time. Hoping that it gets accepted and a new version 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
[JIRA] (JENKINS-11025) Allow the build to fail on low coverage
Ravi Teja Lokineni commented on JENKINS-11025 Allow the build to fail on low coverage @Podar can you ask this on the jenkins mailing list probably someone might respond This message is automatically generated by JIRA. 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-13549) Duplicate test results are shown for grails projectsgr
[ https://issues.jenkins-ci.org/browse/JENKINS-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162881#comment-162881 ] Ravi Teja Lokineni commented on JENKINS-13549: -- This started happening recently. Will update that configuration and see. > Duplicate test results are shown for grails projectsgr > -- > > Key: JENKINS-13549 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13549 > Project: Jenkins > Issue Type: Bug > Components: core, grails >Reporter: Ravi Teja Lokineni >Assignee: jeffg2one > Labels: grails > Attachments: dup_tests.png, dup_tests_1.png, dup_tests_1.png > > > This started happening recently. PFA the attached screenshots. Each failed > testcase is printed twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13549) Duplicate test results are shown for grails projectsgr
[ https://issues.jenkins-ci.org/browse/JENKINS-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Teja Lokineni updated JENKINS-13549: - Attachment: dup_tests_1.png > Duplicate test results are shown for grails projectsgr > -- > > Key: JENKINS-13549 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13549 > Project: Jenkins > Issue Type: Bug > Components: core, grails >Reporter: Ravi Teja Lokineni >Assignee: jeffg2one > Labels: grails > Attachments: dup_tests.png, dup_tests_1.png, dup_tests_1.png > > > This started happening recently. PFA the attached screenshots. Each failed > testcase is printed twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13549) Duplicate test results are shown for grails projectsgr
Ravi Teja Lokineni created JENKINS-13549: Summary: Duplicate test results are shown for grails projectsgr Key: JENKINS-13549 URL: https://issues.jenkins-ci.org/browse/JENKINS-13549 Project: Jenkins Issue Type: Bug Components: core, grails Reporter: Ravi Teja Lokineni Assignee: jeffg2one Attachments: dup_tests.png, dup_tests_1.png This started happening recently. PFA the attached screenshots. Each failed testcase is printed twice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8326) Support for ratcheting
[ https://issues.jenkins-ci.org/browse/JENKINS-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161270#comment-161270 ] Ravi Teja Lokineni commented on JENKINS-8326: - I reopened JENKINS-11025 based on your comments. IMHO I don't think this plugin is developed actively. > Support for ratcheting > -- > > Key: JENKINS-8326 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8326 > Project: Jenkins > Issue Type: New Feature > Components: cobertura >Reporter: johnsmart >Assignee: stephenconnolly > > It would be very useful to add support for ratcheting. This would involve > making the build job fail or become unstable if the code coverage for a build > drops below the code coverage of the previous build. The plugin could keep > track of the highest code coverage metrics values from previous builds, and > check against this. If the current results are lower, the build fails. If > not, the latest values are stored as the new reference values. > This is very useful for legacy projects, where you want to adopt a Continuous > Improvement strategy rather than just imposing a minimum required level of > test coverage. > Thoughts? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11025) Allow the build to fail on low coverage
[ https://issues.jenkins-ci.org/browse/JENKINS-11025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Teja Lokineni reopened JENKINS-11025: -- As per the [comment|https://issues.jenkins-ci.org/browse/JENKINS-8326?focusedCommentId=161244&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-161244] this doesn't seem to be a duplicate > Allow the build to fail on low coverage > --- > > Key: JENKINS-11025 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11025 > Project: Jenkins > Issue Type: New Feature > Components: cobertura >Affects Versions: current > Environment: Jenkins Cobertura Plugin: 1.3 > Jenkins: 1.430 > Grails Cobertura plugin for code coverage in the project >Reporter: Ravi Teja Lokineni >Assignee: stephenconnolly > Fix For: current > > > Suppose my code coverage is below 80%. I want the build to be marked as > failure by providing an option on the job page or so. > I think right now it's providing only the change of icons for low coverage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
