[JIRA] (JENKINS-51556) xUnit JEP-200 incompatibility
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-51556
xUnit JEP-200 incompatibility
Change By:
Nikolas Falco
xUnit plugin will not parse Gherkin xml output because of JEP-200 issue {noformat} *17:33:49* [xUnit] [INFO] - [NUnit-2 (default)] - 6 test report file(s) were found with the pattern 'tests\ results results_LATEST_ \ _LATEST_\ GherkinTest \ *\TestResult.xml' relative to 'd:\Jenkins\workspace\Test_xUnitPlugin' for the testing framework 'NUnit-2 (default)'.*17:33:49* [xUnit] [ERROR] - Conversion error Error to convert the input XML document*17:33:49* ERROR: Step 'Publish xUnit test result report' aborted due to exception: *17:33:49* java.lang.SecurityException: Rejected: net.sf.saxon.expr.CardinalityChecker; see [https://jenkins.io/redirect/class-filter/]*17:33:49* at hudson.remoting.ClassFilter.check(ClassFilter.java:76)*17:33:49* at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:129)*17:33:49* at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readClassDesc(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readObject0(Unknown Source)*17:33:49* at java.io.ObjectInputStream.defaultReadFields(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readSerialData(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readObject0(Unknown Source)*17:33:49* at java.io.ObjectInputStream.defaultReadFields(Unknown Source)*17:33:49* at java.io.ObjectInputStream.defaultReadObject(Unknown Source)*17:33:49* at java.lang.Throwable.readObject(Unknown Source)*17:33:49* at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source)*17:33:49* at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)*17:33:49* at java.lang.reflect.Method.invoke(Unknown Source)*17:33:49* at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readSerialData(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readObject0(Unknown Source)*17:33:49* at java.io.ObjectInputStream.defaultReadFields(Unknown Source)*17:33:49* at java.io.ObjectInputStream.defaultReadObject(Unknown Source)*17:33:49* at java.lang.Throwable.readObject(Unknown Source)*17:33:49* at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source)*17:33:49* at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)*17:33:49* at java.lang.reflect.Method.invoke(Unknown Source)*17:33:49* at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readSerialData(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)*17:33:49* at java.io.ObjectInputStream.readObject0(Unknown Source)*17:33:49* at java.io.ObjectInputStream.defaultReadFields(Unknown Source)*
[JIRA] (JENKINS-51556) xUnit JEP-200 incompatibility
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-51556
xUnit JEP-200 incompatibility
Change By:
Nikolas Falco
xUnit plugin will not parse Gherkin xml output because of JEP-200 issue{noformat} *17:33:49* [xUnit] [INFO] - [NUnit-2 (default)] - 6 test report file(s) were found with the pattern 'tests\results_LATEST_\GherkinTest*\TestResult.xml' relative to 'd:\Jenkins\workspace\Test_xUnitPlugin' for the testing framework 'NUnit-2 (default)'. *17:33:49* [xUnit] [ERROR] - Conversion error Error to convert the input XML document *17:33:49* ERROR: Step 'Publish xUnit test result report' aborted due to exception: *17:33:49*java.lang.SecurityException: Rejected: net.sf.saxon.expr.CardinalityChecker; see[https://jenkins.io/redirect/class-filter/] *17:33:49* at hudson.remoting.ClassFilter.check(ClassFilter.java:76) *17:33:49* at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:129) *17:33:49* at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readClassDesc(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readObject0(Unknown Source) *17:33:49* at java.io.ObjectInputStream.defaultReadFields(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readSerialData(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source Sorce ) *17:33:49* at java.io.ObjectInputStream.readObject0(Unknown Source) *17:33:49* at java.io.ObjectInputStream.defaultReadFields(Unknown Source) *17:33:49* at java.io.ObjectInputStream.defaultReadObject(Unknown Source) *17:33:49* at java.lang.Throwable.readObject(Unknown Source) *17:33:49* at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source) *17:33:49* at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) *17:33:49* at java.lang.reflect.Method.invoke(Unknown Source) *17:33:49* at java.io.ObjectStreamClass.invokeReadObject(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readSerialData(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readObject0(Unknown Source) *17:33:49* at java.io.ObjectInputStream.defaultReadFields(Unknown Source) *17:33:49* at java.io.ObjectInputStream.defaultReadObject(Unknown Source) *17:33:49* at java.lang.Throwable.readObject(Unknown Source) *17:33:49* at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source) *17:33:49* at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) *17:33:49* at java.lang.reflect.Method.invoke(Unknown Source) *17:33:49* at java.io.ObjectStreamClass.invokeReadObject(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readSerialData(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) *17:33:49* at java.io.ObjectInputStream.readObject0(Unknown Source) *17:33:49* at
[JIRA] (JENKINS-51481) Parse error occur when NUnit report have categories
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-51481 Parse error occur when NUnit report have categories Change By: Nikolas Falco Summary: nUnit Import: 'Conversion Parse error Error to convert the input XML document' with 2.0.0 occur when NUnit report have categories Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51481) Parse error occur when NUnit report have categories
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-51481 Parse error occur when NUnit report have categories Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51556) xUnit JEP-200 incompatibility
Title: Message Title Nikolas Falco commented on JENKINS-51556 Re: xUnit JEP-200 incompatibility I have to test locally with a slave node and understand why there is this serialisation issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51645) Add support for claims plugin in xUnit
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-51645 Add support for claims plugin in xUnit Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30710) xUnit plugin to do case insensitive xsd validation
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-30710 xUnit plugin to do case insensitive xsd validation Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30710) xUnit plugin to do case insensitive xsd validation
Title: Message Title Nikolas Falco closed an issue as Won't Do This cause issue in the XML parser because it is case sensitive. Jenkins / JENKINS-30710 xUnit plugin to do case insensitive xsd validation Change By: Nikolas Falco Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40505) Fail test if no tests ran
Title: Message Title Nikolas Falco resolved as Fixed Use the new Passed Threshold to fail the build in case the total number of test is less or equals the threshold (in this case 0) Jenkins / JENKINS-40505 Fail test if no tests ran Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52893) Better error handling for InvalidStateException in xuint plugin
Title: Message Title Nikolas Falco resolved as Fixed Now we use directly the method to perform merge of result without reflection Jenkins / JENKINS-52893 Better error handling for InvalidStateException in xuint plugin Change By: Nikolas Falco Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52963) Provide list of invalid xml files in build output (or provide option for this)
Title: Message Title Nikolas Falco commented on JENKINS-52963 Re: Provide list of invalid xml files in build output (or provide option for this) Which is the version of plugin do you installed? Should be already so. I refactor the log some version ago, it logs always on console log both XSD validation errors and XSLT transformation errors. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52908) Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-52908 Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52711) Xunit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Nikolas Falco commented on JENKINS-52711 Re: Xunit Results Trend graph doesn't show all build results if builds have been deleted XUnit use the TestResultAction of junit plugin (1.24) that has the same behavior (tested just now). It suppose there are no gaps between builds and for me have sense (what is the reason to remove manually a build?) In TestNG plugin (JENKINS-32746) owner has decide to patch locally. If the owner of JUnit plugin decides is a bug and fix the issue, it will available for all plugin that use junit like xunit. I'm reassign the issue to junit plugin. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52711) Xunit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Nikolas Falco edited a comment on JENKINS-52711 Re: Xunit Results Trend graph doesn't show all build results if builds have been deleted XUnit use the TestResultAction of junit plugin (1.24) that has the same behavior (tested just now). It suppose there are no gaps between builds and for me have sense (what is the reason to remove manually a build?)In TestNG plugin (JENKINS-32746) owner has decide to patch locally. If the owner of JUnit plugin decides agree with you it is a bug and fix the issue, it the fix will available for all plugin that use junit like xunit.I'm reassign the issue to junit plugin. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52711) Xunit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52711 Xunit Results Trend graph doesn't show all build results if builds have been deleted Change By: Nikolas Falco Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51993) Failing to parse nunit 2 results file
Title: Message Title Nikolas Falco closed an issue as Cannot Reproduce Jenkins / JENKINS-51993 Failing to parse nunit 2 results file Change By: Nikolas Falco Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52711) Xunit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52711 Xunit Results Trend graph doesn't show all build results if builds have been deleted Change By: Nikolas Falco Component/s: junit-plugin Component/s: xunit-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52711 JUnit Results Trend graph doesn't show all build results if builds have been deleted Change By: Nikolas Falco Summary: Xunit JUnit Results Trend graph doesn't show all build results if builds have been deleted Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52711) Xunit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52711 Xunit Results Trend graph doesn't show all build results if builds have been deleted Change By: Nikolas Falco Component/s: junit-plugin Component/s: xunit-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35699) xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9
Title: Message Title Nikolas Falco closed an issue as Cannot Reproduce Since the caller was changed in recent versions please reopen if happens again. Jenkins / JENKINS-35699 xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9 Change By: Nikolas Falco Status: Open Closed Assignee: Gregory Boissinot Nikolas Falco Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34518) xUnit plugin fails to convert CTest xml
Title: Message Title Nikolas Falco resolved as Fixed With latest version of plugin the attached document can be parsed with success Jenkins / JENKINS-34518 xUnit plugin fails to convert CTest xml Change By: Nikolas Falco Status: Open Resolved Assignee: Gregory Boissinot Nikolas Falco Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24224) improve xunit plugin with test-stability plugin
Title: Message Title Nikolas Falco resolved as Duplicate Add support for TestDataPublisher Jenkins / JENKINS-24224 improve xunit plugin with test-stability plugin Change By: Nikolas Falco Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24224) improve xunit plugin with test-stability plugin
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-24224 improve xunit plugin with test-stability plugin Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52908) Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52908 Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results Change By: Nikolas Falco Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52908) Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results
Title: Message Title Nikolas Falco resolved as Fixed Down to minor because it's cospetic and does not prevent functionality of the build Jenkins / JENKINS-52908 Newlines get ignored in failure message and possibly stack trace when uploading xUnitDotNet xml results Change By: Nikolas Falco Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52814) Build status set to failed but not failed immediately
Title: Message Title Nikolas Falco closed an issue as Not A Defect It works as design, the XUnit builder/publisher marks the build status in agreement with the values of thresholds. Only the builder (deprecated) abort the build in case of errors when process reports and the option 'Stop and set the build to 'failed' status if there are errors when processing a result file' is enabled Jenkins / JENKINS-52814 Build status set to failed but not failed immediately Change By: Nikolas Falco Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title Nikolas Falco commented on JENKINS-53036 Re: NULL pointer exception when parsing JUnit files created with phpunit It's very strange that NPE because all cases seems covered. Could you please send me the job configuration? The issue is not related to the report file. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53036) NULL pointer exception when parsing JUnit files created with phpunit
Title: Message Title Nikolas Falco commented on JENKINS-53036 Re: NULL pointer exception when parsing JUnit files created with phpunit I got it seems happens on non pipeline job with old configuration Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53036) NPE after upgrade to 2.2.1 when run publisher
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53036 NPE after upgrade to 2.2.1 when run publisher Change By: Nikolas Falco Summary: NULL pointer exception NPE after upgrade to 2.2.1 when parsing JUnit files created with phpunit run publisher Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53036) NPE after upgrade to 2.2.1 when run publisher
Title: Message Title Nikolas Falco started work on JENKINS-53036 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53036) NPE after upgrade to 2.2.1 when run publisher
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-53036 NPE after upgrade to 2.2.1 when run publisher Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53036) NPE after upgrade to 2.2.1 when run publisher
Title: Message Title Nikolas Falco commented on JENKINS-53036 Re: NPE after upgrade to 2.2.1 when run publisher Fixed in 2.2.2 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53034) xUnit plugin fails to parse NUnit 2 report format generated by NUnit
Title: Message Title Nikolas Falco commented on JENKINS-53034 Re: xUnit plugin fails to parse NUnit 2 report format generated by NUnit In the previous issue you wrote that you enable NUnit 2.x format because NUnit 3.x was not enable. What's happens if you produce the use NUnit 3.x. Which tools produce the NUnit 2.x format? The issue seems to be that the report file contains a concat of more assemblies and this does not respect the original schema files. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50658) xUnit does not support the flaky surefire tests generated by maven with rerun property
Title: Message Title Nikolas Falco commented on JENKINS-50658 Re: xUnit does not support the flaky surefire tests generated by maven with rerun property Yes, the original XSD published on apache was not correct (tracked on SUREFIRE-1550). The schema is updated and released in latest plugin version 2.2.1 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53034) xUnit plugin fails to parse NUnit 2 report format generated by NUnit
Title: Message Title Nikolas Falco commented on JENKINS-53034 Re: xUnit plugin fails to parse NUnit 2 report format generated by NUnit Thank for the details. The XSD I'm using comes from the NUnit 2.6 distribution zip (source here) In the meanwhile I can relax the constraint. Please open an issue to the NUnit Console because produce a NUnit 2.x format not compliant with their NUnit 2.6.4 schema. It's better if you open the issue instead of me since you are more confident with the C# tools in case of technical question or on how to reproduce the issue. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53034) xUnit plugin fails to parse NUnit 2 report format generated by NUnit
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-53034 xUnit plugin fails to parse NUnit 2 report format generated by NUnit Change By: Nikolas Falco Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53034) Failure when validate NUnit 2.x reports generated by NUnit 3.x console
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53034 Failure when validate NUnit 2.x reports generated by NUnit 3.x console Change By: Nikolas Falco Summary: xUnit plugin fails to parse Failure when validate NUnit 2 report format .x reports generated by NUnit 3.x console Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53115) Failure to parse JUnit after upgrading from 1.104 to 2.2.3
Title: Message Title Nikolas Falco commented on JENKINS-53115 Re: Failure to parse JUnit after upgrading from 1.104 to 2.2.3 Miss the required errors attribute on testsuite element. Refer to the wiki about changes in 2.x Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53115) Failure to parse JUnit after upgrading from 1.104 to 2.2.3
Title: Message Title Nikolas Falco closed an issue as Not A Defect Jenkins / JENKINS-53115 Failure to parse JUnit after upgrading from 1.104 to 2.2.3 Change By: Nikolas Falco Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Nikolas Falco closed an issue as Fixed The nunit version must be a valid version because in XSLT there are logics on how construct the classname and name of test case. Depending on the version some attributes or xml elements are not present. Please fill a bug to the tools to declare against which version of NUnit is compatible. Jenkins / JENKINS-53165 Conversion Exception for NUnit2 XML Format when nunit-version is a String Change By: Nikolas Falco Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Nikolas Falco commented on JENKINS-53165 Re: Conversion Exception for NUnit2 XML Format when nunit-version is a String Depends on the NUnit version. The most recent writes only the version number with exception of NUnit 2.2 that does not have environment XML element. Remember that the version should be 2.x, if you see 3.x are adapter of NUnit 3.x to write in NUnit 2 format. Here you can find examples gathered from JIRA issues. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Nikolas Falco commented on JENKINS-53165 Re: Conversion Exception for NUnit2 XML Format when nunit-version is a String Anyway in the github repo you linked above seems has used a specific XSD file. To know which is the correct version to write you should check which XSD version is that. You can find all NUnit XSD version to compare here (ignore the nunit-2.x.xsd file) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Nikolas Falco commented on JENKINS-53165 Re: Conversion Exception for NUnit2 XML Format when nunit-version is a String By a quick compare seems version 2.5 (or 2.6 since the XSD are the same) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures reported as Success when using nunit3-console with nunit2 output formatter
Title: Message Title Nikolas Falco commented on JENKINS-53186 Re: Test Failures reported as Success when using nunit3-console with nunit2 output formatter If you produce the NUnit3 why do you convert to NUni2 instead of configure the tool type to NUnit 3.x? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures reported as Success when using nunit3-console with nunit2 output formatter
Title: Message Title Nikolas Falco commented on JENKINS-53186 Re: Test Failures reported as Success when using nunit3-console with nunit2 output formatter Anyway let me have a look if result Error is a valid kind in NUnit2 and in case handle properly or it is a status in NUnit3 that is handled in wrong manner in the converter. I suggest if you have NUni3 to do not convert and use the tool type set to NUnit 3.x Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures reported as Success when using nunit3-console with nunit2 output formatter
Title: Message Title Nikolas Falco commented on JENKINS-53186 Re: Test Failures reported as Success when using nunit3-console with nunit2 output formatter "my first impression was that the "nunit-version" field (which is set to "3.5.0.0" in the attached example) might get interpreted" This is a bug of adapter https://github.com/nunit/nunit-v2-result-writer/issues/11 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53186 NUnit 2.x test cases with result Error are reported as Success Change By: Nikolas Falco Summary: Test Failures NUnit 2.x test cases with result Error are reported as Success when using nunit3-console with nunit2 output formatter Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Nikolas Falco started work on JENKINS-53186 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Nikolas Falco updated JENKINS-53186 Jenkins / JENKINS-53186 NUnit 2.x test cases with result Error are reported as Success Change By: Nikolas Falco Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28490) jUnit discarding tags when certain attributes are equal
Title: Message Title Nikolas Falco assigned an issue to Unassigned Jenkins / JENKINS-28490 jUnit discarding tags when certain attributes are equal Change By: Nikolas Falco Assignee: Gregory Boissinot Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40765) Make Release Plugin compatible with pipeline
Title: Message Title Nikolas Falco commented on JENKINS-40765 Re: Make Release Plugin compatible with pipeline The title of this issue it's misleading because it's not a real support to describe a steps and parameter of a release wrapper but enable call release job of of other non pipeline job. Since there is not documentation and a bug that prevent to have a pipeline syntax after spent 2g I realise this plugin could not be used to release a pipeline job with extra parameters and pre/post build steps Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Nikolas Falco updated JENKINS-53186 released in 2.2.4 Jenkins / JENKINS-53186 NUnit 2.x test cases with result Error are reported as Success Change By: Nikolas Falco Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Attachment: input.xsl Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Attachment: input.xsl Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Attachment: custom-to-junit.xsl Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52392) Support custom junit format that does not respect any precise schema
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-52392 Support custom junit format that does not respect any precise schema Change By: Nikolas Falco Since 2.x the official supported JUnit report schemas are the most used in Java world (ant and maven surefire).The breaking changes was introduce (since 2.x using semantic versioning), a warning is shown in the Jenkins plugin page and all details provided in the [Wiki page|https://wiki.jenkins.io/display/JENKINS/xUnit+Plugin]To provide supports for the who use tools which declare to produce a JUnit report that is not strict to any official schema, the procedure is configure the xUnit plugin select the "Custom Tool" as test type and provide the path to a custom XSL (it will be provided by this plugin as attachment and documented in Wiki page) in the "custom stylesheet" textbox. The path of the XSL file that can be absolute on the server (jenkins master) or relative to the workspace or an URL ([see the wiki page for more details|https://wiki . jenkins.io/display/JENKINS/xUnit+Plugin#xUnitPlugin-CustomXSL]). The XSL is free and could be customised to fit every extra needs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-53463) NodeJS plugin - NodeJS installation not working correctly
Title: Message Title Nikolas Falco commented on JENKINS-53463 Re: NodeJS plugin - NodeJS installation not working correctly This happens because you have already a NodeJS installed in the machine and its bin path is before in the PATH variable. The only way is to uninstall embedded NodeJS installation, because by design the NodeJS path is always happend to the PATH variable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53463) NodeJS plugin - NodeJS installation not working correctly
Title: Message Title Nikolas Falco edited a comment on JENKINS-53463 Re: NodeJS plugin - NodeJS installation not working correctly This happens because you have already a NodeJS installed in the machine and its bin path is before that one contributed by the plugin in the PATH variable. The only way is to uninstall embedded NodeJS installation, because by design the NodeJS any tool path is always happend append at the end to the system PATH variable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53635) xunit step failure is not displayed
Title: Message Title Nikolas Falco updated JENKINS-53635 Jenkins / JENKINS-53635 xunit step failure is not displayed Change By: Nikolas Falco Status: In Review Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53635) xunit step failure is not displayed
Title: Message Title Nikolas Falco commented on JENKINS-53635 Re: xunit step failure is not displayed Publishers (or Recorder) like xunit (and junit) does not stop the build. Normally in a standard project they are post build steps and all of them are executed. In a pipeline you can mix them but the behavior is the same, a failure does not cause the pipeline to stop. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53619) Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1
Title: Message Title Nikolas Falco commented on JENKINS-53619 Re: Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1 There is no description about the issue, when this happens, nothing to reproduce, unknow version of nodejs plugin or jenkins... For what I can see there is only a WARNING log (not error) mixed to a heap dump (maybe), all not preformed (JIRA has a lot richtext options). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53619) Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-53619
Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1
Change By:
Nikolas Falco
When a new installation of NodeJS tools occurs I see had notice a warning in the console log that refers to a jenkins page about "Serialization of anonymous classes" WARNING: Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1 in file:/var/hudson/master/plugins/nodejs/WEB-INF/lib/nodejs.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Sep 17, 2018 11:28:45 AM hudson.model.Run execute javap -classpath /var/hudson/master/plugins/nodejs/WEB-INF/lib/nodejs.jar -l "jenkins.plugins.nodejs.tools.NodeJSInstallation$1"Compiled from "NodeJSInstallation.java"public class jenkins.plugins.nodejs.tools.NodeJSInstallation extends hudson.tools.ToolInstallation implements hudson.model.EnvironmentSpecific, hudson.slaves.NodeSpecific { public jenkins.plugins.nodejs.tools.NodeJSInstallation(java.lang.String, java.lang.String, java.util.List>); LineNumberTable: line 71: 0 line 72: 8 LocalVariableTable: Start Length Slot Name Signature 0 9 0 this Ljenkins/plugins/nodejs/tools/NodeJSInstallation; 0 9 1 name Ljava/lang/String; 0 9 2 home Ljava/lang/String; 0 9 3 properties Ljava/util/List;protected jenkins.plugins.nodejs.tools.NodeJSInstallation(java.lang.String, java.lang.String, java.util.List>, jenkins.plugins.nodejs.tools.Platform); LineNumberTable: line 75: 0 line 76: 13 line 77: 19 LocalVariableTable: Start Length Slot Name Signature 0 20 0 this Ljenkins/plugins/nodejs/tools/NodeJSInstallation; 0 20 1 name Ljava/lang/String; 0 20 2 home Ljava/lang/String; 0 20 3 properties Ljava/util/List; 0 20 4 platform Ljenkins/plugins/nodejs/tools/Platform;public jenkins.plugins.nodejs.tools.NodeJSInstallation forEnvironment(hudson.EnvVars); LineNumberTable: line 85: 0 LocalVariableTable: Start Length Slot Name Signature 0 31 0 this Ljenkins/plugins/nodejs/tools/NodeJSInstallation; 0 31 1 environment Lhudson/EnvVars;public jenkins.plugins.nodejs.tools.NodeJSInstallation forNode(hudson.model.Node, hudson.model.TaskListener) throws java.io.IOException, java.lang.InterruptedException; LineNumberTable: line 94: 0 LocalVariableTable: Start Length Slot Name Signature 0 29 0 this Ljenkins/plugins/nodejs/tools/NodeJSInstallation; 0 29 1 node Lhudson/model/Node; 0 29 2 log Lhudson/model/TaskListener;public void buildEnvVars(hudson.EnvVars); LineNumberTable: line 103: 0 line 104: 5 line 105: 9 line 107: 10 line 108: 18 line 109: 29 LocalVariableTable: Start Length Slot Name Signature 0 30 0 this Ljenkins/plugins/nodejs/tools/NodeJSInstallation; 0 30 1 env Lhudson/EnvVars; 5 25 2 home Ljava/lang/String;public java.lang.String getExecutable(hudson.Launcher) throws java.lang.InterruptedException, java.io.IOException; LineNumberTable: line 123: 0 LocalVariableTable: Start Length Slot Name Signature 0 21 0 this Ljenkins/plugins/nodejs/tools/NodeJSInstallation; 0 21 1 launcher Lhudson/
[JIRA] (JENKINS-53619) Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-53619
Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1
Change By:
Nikolas Falco
When a new installation of NodeJS tools occurs I see had notice a warning in the console log that refers to a jenkins page about "Serialization of anonymous classes" {noformat} WARNING: Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1 in file:/var/hudson/master/plugins/nodejs/WEB-INF/lib/nodejs.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53619) Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53619 Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1 Change By: Nikolas Falco Environment: Jenkins 2.102NodeJS 1.2.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53619) Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1
Title: Message Title Nikolas Falco updated JENKINS-53619 Jenkins / JENKINS-53619 Attempt to (de-)serialize anonymous class jenkins.plugins.nodejs.tools.NodeJSInstallation$1 Change By: Nikolas Falco Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53635) xunit step failure is not displayed
Title: Message Title Nikolas Falco commented on JENKINS-53635 Re: xunit step failure is not displayed The link you are speaking in the PR is done for steps that does not handle build status it self. Have a look to other publish strategy, none of them throws exception. hudson.tasks.Fingerprinter.perform() hudson.tasks.ArtifactArchiver.perform() hudson.tasks.Mailer.perform() (perform an e.printStackTrace to listener -> console) hudson.plugins.sonar.SonarPublisher.perform() -> (exception captured and handled in executeSonar()) ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53707) Allow commit message and author of head commit
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-53707 Allow commit message and author of head commit Issue Type: New Feature Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2018-09-21 13:27 Environment: Jenkins 2.138 bitbucket source branch plugin 2.2.12 Priority: Major Reporter: Nikolas Falco Expose commit message and author for head commit, this allows implementation of traits based on commit (inside the plugin or as extension in other plugins). The scenario to cover is when in the pipeline there are git commit (for example during release) and push that triggers multiple build. In my scenario are three builds: one for the push of new version one for the push of tag (JENKINS-51063) one for the push of next development version We would prevent new job if commit was performed by a specific user (jenkins user) or contains a particular message (for example start with [maven-release-plugin]). Author is retrieved but are not exposed to by the BitbucketCommit interface, the message is not correctly handled so it's always null. After that we could add a CommitFilter(out)Traits that can exclude branches that matches some rules based on author name (typical representation of commit author in git) or message.
[JIRA] (JENKINS-53707) Allow commit message and author of head commit
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-53707
Allow commit message and author of head commit
Change By:
Nikolas Falco
Expose commit message and author for head commit, this allows implementation of traits based on commit (inside the plugin or as extension in other plugins).The scenario to cover is when in the pipeline there are git commit (for example during release) and push that triggers multiple build.In my scenario are three builds:- one for the push of new version - one for the push of tag (JENKINS-51063)- one for the push of next development versionWe would prevent trigger new build job if commit was performed by a specific user (jenkins user) or contains a particular message (for example start with [maven-release-plugin]).Author is retrieved but are not exposed to by the BitbucketCommit interface, the message is not correctly handled so it's always null.After that we *could* add a CommitFilter(out)Traits that can exclude branches that matches some rules based on author {{name }} (typical representation of commit author in git) or message.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googl
[JIRA] (JENKINS-53707) Allow commit message and author of head commit
Title: Message Title Nikolas Falco commented on JENKINS-53707 Re: Allow commit message and author of head commit Work in progress here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53731) Include jackson-annotations
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-53731 Include jackson-annotations Issue Type: New Feature Assignee: Devin Nusbaum Components: jackson2-api-plugin Created: 2018-09-22 10:36 Priority: Major Reporter: Nikolas Falco Some plugins that have to parse response from REST has annotated its java bean with jackson annotation to make easier the mapping. These annotations are in a separate bundle jackson-annotations that is missing by this plugins (Jackson propetary annotations are more powerfull than JAXB, this also avoid migrate existing code) Add Comment
[JIRA] (JENKINS-53731) Include jackson-annotations
Title: Message Title Nikolas Falco closed an issue as Done My fault, my points to the jackson 1 package annotations, this was the reason I suppose the jar was not included in this plugin. I'm sorry. Jenkins / JENKINS-53731 Include jackson-annotations Change By: Nikolas Falco Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53731) Include jackson-annotations
Title: Message Title Nikolas Falco edited a comment on JENKINS-53731 Re: Include jackson-annotations My fault, my points to the code had import jackson 1 package annotations, this was the reason I suppose the jar was not included in this plugin.I'm sorry. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53635) xunit step failure is not displayed
Title: Message Title Nikolas Falco updated JENKINS-53635 Jenkins / JENKINS-53635 xunit step failure is not displayed Change By: Nikolas Falco Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45826) XUnit support for distinguishing test reports from different steps
Title: Message Title Nikolas Falco assigned an issue to Andrew Bayer Jenkins / JENKINS-45826 XUnit support for distinguishing test reports from different steps Change By: Nikolas Falco Assignee: Nikolas Falco Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53707) Allow commit message and author of head commit
Title: Message Title Nikolas Falco commented on JENKINS-53707 Re: Allow commit message and author of head commit Proposed PR here https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/145 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45826) XUnit support for distinguishing test reports from different steps
Title: Message Title Nikolas Falco updated JENKINS-45826 Jenkins / JENKINS-45826 XUnit support for distinguishing test reports from different steps Change By: Nikolas Falco Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45826) XUnit support for distinguishing test reports from different steps
Title: Message Title Nikolas Falco updated JENKINS-45826 Jenkins / JENKINS-45826 XUnit support for distinguishing test reports from different steps Change By: Nikolas Falco Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45826) XUnit support for distinguishing test reports from different steps
Title: Message Title Nikolas Falco updated JENKINS-45826 Jenkins / JENKINS-45826 XUnit support for distinguishing test reports from different steps Change By: Nikolas Falco Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53635) xunit step failure is not displayed
Title: Message Title Nikolas Falco updated JENKINS-53635 Jenkins / JENKINS-53635 xunit step failure is not displayed Change By: Nikolas Falco Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23336) xunit plugin documentation is out of date
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-23336 xunit plugin documentation is out of date Change By: Nikolas Falco Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51063) Multibranch pipeline does not handle correctly webhook of kind tag created
Title: Message Title Nikolas Falco commented on JENKINS-51063 Re: Multibranch pipeline does not handle correctly webhook of kind tag created The branch is intended to trigger a new build for discovered branch job. If you mean that you have "Discover Tags" and the web-hook does not trigger a build it is possible since the Tag job was merged after this issue and PR. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45502) Add concept of "interesting" to SCMHead and SCMRevision
Title: Message Title Nikolas Falco commented on JENKINS-45502 Re: Add concept of "interesting" to SCMHead and SCMRevision Stephen Connolly I'm interessed about you idea of scalar instead of boolean returned from a possible new API SCMSourceContext.skipEvent (or Build). In case of scalar the people that configure a job how could know which are value contributed by each SCMEventFilter and how this impact the final value of the scalar to match against the cute-off? I'm asking because recently I had implement release as pipeline and to avoid trigger multiple builds with something similar of JENKINS-41048 (here) I skip some kinds of events (more details here) but this marks the branch (master) to remove. This feature is required for our organisation and seems froosen from long time. I have budget to implement this and I would some clarification to propose something of acceptable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-53994 Parameters that use own descriptor to check/fill fields returns 404 in schedule release page Issue Type: New Feature Assignee: Oleg Nenashev Components: release-plugin Created: 2018-10-10 16:56 Environment: Jenkins 2.121.3 release-plugin 2.10.1 Priority: Major Reporter: Nikolas Falco If I define a new parameters like validation string parameter that use a regex to validate the user input it performs a doCheckXYZ method of its descriptor. In the Schedule Release Page (action page) the HTTP request returns 404 because the URL is relative to the action page $JENKINS_URL/jobs/XYZ/release instead of the project. Add Comment
[JIRA] (JENKINS-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Nikolas Falco commented on JENKINS-53994 Re: Parameters that use own descriptor to check/fill fields returns 404 in schedule release page Oleg Nenashev I know that you mark yourself as retired developer of this plugin (and you are usually busy) but the solution is really fast and already proposed here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Nikolas Falco edited a comment on JENKINS-53994 Re: Parameters that use own descriptor to check/fill fields returns 404 in schedule release page [~oleg_nenashev] I know that you had mark yourself as retired developer of this plugin (and you are usually busy) but the solution is really fast and already proposed [here|https://github.com/jenkinsci/release-plugin/pull/31] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53994 Parameters that use own descriptor to check/fill fields returns 404 in schedule release page Change By: Nikolas Falco Attachment: schedule_build_page_exception.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47308) Branch Build Strategy should be able to apply to revisions
Title: Message Title Nikolas Falco commented on JENKINS-47308 Re: Branch Build Strategy should be able to apply to revisions This issue could be marked as Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47311) If a BranchBuildStrategy extension is defined, BranchSource config is broken
Title: Message Title Nikolas Falco commented on JENKINS-47311 Re: If a BranchBuildStrategy extension is defined, BranchSource config is broken Also this issue could be marked as fixed since it is merge into master and released in 2.0.13 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47308) Branch Build Strategy should be able to apply to revisions
Title: Message Title Nikolas Falco updated JENKINS-47308 Released in 2.0.12 (maybe the github commit integration (FIXED) did not work as expected) Jenkins / JENKINS-47308 Branch Build Strategy should be able to apply to revisions Change By: Nikolas Falco Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47311) If a BranchBuildStrategy extension is defined, BranchSource config is broken
Title: Message Title Nikolas Falco updated JENKINS-47311 Released in 2.0.12 (maybe the github commit integration (FIXED) did not work as expected) Jenkins / JENKINS-47311 If a BranchBuildStrategy extension is defined, BranchSource config is broken Change By: Nikolas Falco Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix > Tibor DiganaThe fact that Jenkins plugins are parsing this XML without any problem means that they do not mind in the elements of (rerunError, rerunFailure, flakyFailure, flakyError) Not true at all, plugins like xunit use the XSD to validate the XML (and with 2.22.1 is broken, files are skipped). It's not clear for me what is the gain of the stacktrace element and make rerun elements different from failure and error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Nikolas Falco Component/s: flaky-test-handler-plugin Component/s: xunit-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco edited a comment on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix > [~tibor17]The fact that Jenkins plugins are parsing this XML without any problem means that they do not mind in the elements of (rerunError, rerunFailure, flakyFailure, flakyError)Not true at all, plugins like xunit use the XSD to validate the XML (and with 2.22.1 is broken, files are skipped). It's not clear for me what is the gain of the stacktrace element and make rerun elements different from failure and error. EDIT: you missed to list the component that supports flaky elements... xunit and flaky-test-handler and for this reason you did get a response in time because no one of major interested people was informed. I'm here now because the new version had broken our organisation pipelines and I got this link from SUREFIRE-1559. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco assigned an issue to Damian Szczepanik Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Nikolas Falco Assignee: Tibor Digana Damian Szczepanik Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53927) Jenkins Build opens up multiple Chrome instances
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53927 Jenkins Build opens up multiple Chrome instances Change By: Nikolas Falco Component/s: xunit-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53927) Jenkins Build opens up multiple Chrome instances
Title: Message Title Nikolas Falco commented on JENKINS-53927 Re: Jenkins Build opens up multiple Chrome instances I do not understand steps to reproduce this bug. > chrome instances that get opened by a Jenkins build the xunit plugin does not open external programs (the same I think also the other plugins you list). Please attach the entire console log (no doc, no images just a txt file with the copy/paste of console log output) and also a little example of your jenkins job Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54228) xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-54228 xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1 Change By: Nikolas Falco Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54228) xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-54228 xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1 Issue Type: New Feature Assignee: Nikolas Falco Components: xunit-plugin Created: 2018-10-24 18:42 Priority: Major Reporter: Nikolas Falco During a maven build upgrading the maven-surefire-plugin to version 2.22.1 xunit is not able to validate the report if the rerun feature is enabled. Add Comment This message was sent by Atlassia
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Nikolas Falco Component/s: xunit-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
