[JIRA] (JENKINS-46553) Maven surefire timeout treated as successful build
Title: Message Title
Tibor Digana edited a comment on JENKINS-46553
Re: Maven surefire timeout treated as successful build
[~bondolo][~famod]We cannot modify the purpose of *{{maven.test.failure.ignore}}* .Let's explain it: The test set will end up with Result Set (total, failures, errors, flakes, skipped) and the test frameworks (JUnit, TestNG, etc) provide RunListener sending the test events into the final Result Set. All the teminology you can see in {{ *{{maven.test.failure.ignore}}* {\{ }}talks abou about the failures and it means the Result Set. It has nothing to do with any timeouts and vice versa!If we have to fix this without touching the TXT and XML reports, I am all the ear how.My proposal is to introduce *surefire.failIfTimeout=true* and *failsafe.failIfTimeout=true*. It is complemetary principle to the parameter that we already have with *failIfNoTests=true*. So we control the behavior on fine grained level.Setting *maven.test.failure.ignore**=true* would not bypass the *failIfNoTests=true* and the build fails anyway with not having any tests in the project. The same should be with the timeouts. The only difference are the default values, where _failIfNotests has +false+_, and _failIfTimeout would have +true+_.If the user wants to _avoid +build+ failure due to the plugin,_ run the cmd *mvn test -Dmaven.test.failure.ignore=true -Dsurefire.failIfTimeout=false* If the user wants to _avoid +test+ failure(s)_ run the cmd *mvn test -Dmaven.test.failure.ignore=true* Feel free to comment on this.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed
[JIRA] (JENKINS-46553) Maven surefire timeout treated as successful build
Title: Message Title
Tibor Digana edited a comment on JENKINS-46553
Re: Maven surefire timeout treated as successful build
[~bondolo][~famod]We cannot modify the purpose of *{{maven.test.failure.ignore}}* .Let's explain it: The test set will end up with Result Set (total, failures, errors, flakes, skipped) and the test frameworks (JUnit, TestNG, etc) provide RunListener sending the test events into the final Result Set. All the teminology you can see in *{{maven.test.failure.ignore}}*{ \ { }}talks abou failures and it means the Result Set. It has nothing to do with any timeouts and vice versa!If we have to fix this without touching the TXT and XML reports, I am all the ear how.My proposal is to introduce *surefire.failIfTimeout=true* and *failsafe.failIfTimeout=true*. It is complemetary principle to the parameter that we already have with *failIfNoTests=true*. So we control the behavior on fine grained level.Setting *maven.test.failure.ignore**=true* would not bypass the *failIfNoTests=true* and the build fails anyway with not having any tests in the project. The same should be with the timeouts. The only difference are the default values, where _failIfNotests has +false+_, and _failIfTimeout would have +true+_.If the user wants to completely _avoid +build+ failure due to the plugin ,_ run the cmd *mvn test -Dmaven.test.failure.ignore=true -Dsurefire.failIfTimeout=false* If the user wants to _avoid +test+ failure(s)_ run the cmd *mvn test -Dmaven.test.failure.ignore=true* Feel free to comment on this.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-46553) Maven surefire timeout treated as successful build
Title: Message Title
Tibor Digana commented on JENKINS-46553
Re: Maven surefire timeout treated as successful build
Mike Duigou Falko Modler We cannot modify the purpose of maven.test.failure.ignore . Let's explain it: The test set will end up with Result Set (total, failures, errors, flakes, skipped) and the test frameworks (JUnit, TestNG, etc) provide RunListener sending the test events into the final Result Set. All the teminology you can see in maven.test.failure.ignore{{ }}talks abou failures and it means the Result Set. It has nothing to do with any timeouts and vice versa! If we have to fix this without touching the TXT and XML reports, I am all the ear how. My proposal is to introduce surefire.failIfTimeout=true and failsafe.failIfTimeout=true. It is complemetary principle to the parameter that we already have with failIfNoTests=true. So we control the behavior on fine grained level. Setting maven.test.failure.ignore=true would not bypass the failIfNoTests=true and the build fails anyway with not having any tests in the project. The same should be with the timeouts. The only difference are the default values, where failIfNotests has false, and failIfTimeout would have true. If the user wants to completely avoid build failure, run the cmd mvn test -Dmaven.test.failure.ignore=true -Dsurefire.failIfTimeout=false If the user wants to avoid test failure(s) run the cmd mvn test -Dmaven.test.failure.ignore=true Feel free to comment on this.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe f
[JIRA] (JENKINS-55146) PCT sometimes crashes on Java 11 due to module read errors when using the docker image
Title: Message Title Tibor Digana edited a comment on JENKINS-55146 Re: PCT sometimes crashes on Java 11 due to module read errors when using the docker image [~oleg_nenashev]Regarding the Alpine/BusyBox we made three fixes[https://issues.apache.org/jira/browse/SUREFIRE-1702][https://issues.apache.org/jira/browse/SUREFIRE-1703][https://issues.apache.org/jira/browse/SUREFIRE-1704]and we are finishing the last issue few issues to ct cut a new release version 3.0.0-M4. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196213.154461298.8097.1572836820362%40Atlassian.JIRA.
[JIRA] (JENKINS-55146) PCT sometimes crashes on Java 11 due to module read errors when using the docker image
Title: Message Title Tibor Digana commented on JENKINS-55146 Re: PCT sometimes crashes on Java 11 due to module read errors when using the docker image Oleg Nenashev Regarding the Alpine/BusyBox we made three fixes https://issues.apache.org/jira/browse/SUREFIRE-1702 https://issues.apache.org/jira/browse/SUREFIRE-1703 https://issues.apache.org/jira/browse/SUREFIRE-1704 and we are finishing the last issue to ct a new release version 3.0.0-M4. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196213.154461298.8092.1572836760229%40Atlassian.JIRA.
[JIRA] (JENKINS-46768) GitLab API Key Authentication Error and Usr/Pswd not available in Combo Box
Title: Message Title Tibor Digana closed an issue as Cannot Reproduce Works fine with version 1.5.11. Jenkins / JENKINS-46768 GitLab API Key Authentication Error and Usr/Pswd not available in Combo Box Change By: Tibor Digana Status: Open Closed Assignee: Owen Mehegan Tibor Digana Resolution: Cannot Reproduce 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-55146) PCT sometimes crashes on Java 11 due to module read errors when using the docker image
Title: Message Title Tibor Digana edited a comment on JENKINS-55146 Re: PCT sometimes crashes on Java 11 due to module read errors when using the docker image We will use tcp/ip sockets in Surefire/Failsafe (3.0.0-M4 or M5) instead of interprocess pipes which is nowadays sollution for interprocess communication. 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-55146) PCT sometimes crashes on Java 11 due to module read errors when using the docker image
Title: Message Title Tibor Digana commented on JENKINS-55146 Re: PCT sometimes crashes on Java 11 due to module read errors when using the docker image We use tcp/ip sockets in Surefire/Failsafe (3.0.0-M4 or M5) instead of interprocess pipes which is nowadays sollution for interprocess communication. 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 Tibor Digana commented on JENKINS-54228 Re: xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1 Great job Nikolas Falco I will check it out on my Jenkins. 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 Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Nikolas Falco It's up to you. If you find an issue, I am all the ear. But I do not know if your plugin can recognize the XSD version. I hope it can. 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-55146) PCT crashes on Java 11 in Docker on Maven Surefire 2.20
Title: Message Title Tibor Digana commented on JENKINS-55146 Re: PCT crashes on Java 11 in Docker on Maven Surefire 2.20 Oleg Nenashev For the external users it must be very uncertain to read if we mix unrelated issues. Yes, SUREFIRE-855 was fixed in 2.21.0. The another issue https://issues.apache.org/jira/browse/SUREFIRE-1496 is about Jigsaw modularity, see my comment in SUREFIRE-1496. And third unrelated cause error is in your description in this issue: Caused by: java.util.zip.ZipException: zip END header not found The Surefire is not packaging classes in JAR file. It is the responsibility of maven-jar-plugin. Please see the release 3.1.1 of JAR Plugin we did yesterday, I guess. https://issues.apache.org/jira/browse/MJAR-241 After seen deeper, the path is pointing to JDK, this means the file /pct/jdk11-libs/javax.activation.jar and I would say that Oracle or OpenJDK has to be asked. Check it out again with new version of JAR Plugin and possibly Surefire plugin 3.0.0-M2, but you may try to also switch to another JDK to come over the ZIP 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 Tibor Digana updated JENKINS-53237 Nikolas Falco The version 3.0.0-M2 is available in Maven Central. Can you please adapt your plugin xUnit with the path of XSD? It has a new location https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd and old location for legacy versions https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd I hope this would work for you. Sorry. Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Tibor Digana Status: Open Fixed but Unreleased 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-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Nikolas Falco We are in release Vote for the version 3.0.0-M2 Please join us in the Vote: https://lists.apache.org/thread.html/d44c7a8198e4f4d214211e40909249bcca67bdabd7d476731f2e1665@%3Cdev.maven.apache.org%3E 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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana commented on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished Jesse Glick How can i override MAX_LINES_READ in Jenkinsfile? Could not find a snippet code in documentation, only mentioning the constant in release notes. 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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana commented on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished I have updated all plugins in my Jenkins, and removed the function compressBuildLog() from my Jenkinsfile. Now the logs are back again as expected. Jesse Glick I think there was some environment variable to limit the the log size. Where can I find it? And second question, is the plugin [logfilesizechecker|htthttps://plugins.jenkins.io/logfilesizechecker] safe to use? 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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana edited a comment on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished I have updated all plugins in my Jenkins, and removed the function _compressBuildLog()_ from my _Jenkinsfile_.Now the logs are back again as expected.[~jglick] I think there was some environment variable to limit the the log size. Where can I find it? And second question, is the plugin [logfilesizechecker| htthttps https ://plugins.jenkins.io/logfilesizechecker] safe to use? 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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana updated an issue Jenkins / JENKINS-54678 Logs are lost in Multibranch Pipleline after the build has finished Change By: Tibor Digana Comment: [~jglick]ok, good to know your plan.I would like to have compressed log in e-mail attachments.Would you please add a compression to [emailext|https://wiki.jenkins.io/display/JENKINS/Email-ext+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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana commented on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished Jesse Glick ok, good to know your plan. I would like to have compressed log in e-mail attachments. Would you please add a compression to emailext? 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 Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Nikolas Falco We are near to Surefire 3.0.0-M2 release. I have made a fix for this issue. There is a new XSD version 3.0 and documentation explaining the decisions, see index.apt.vm. I have pushed a branch SUREFIRE-1590 on GitHub. Please review it. Thx. 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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana commented on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished Jesse Glick Who should handle this issue? I am doing an internal workshop in my company about Jenkins on December 3rd and this issue is a big problem. 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-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Tibor Digana created an issue Jenkins / JENKINS-54678 Logs are lost in Multibranch Pipleline after the build has finished Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-11-16 18:45 Environment: Jenkins 2.138.3 Pipeline Multibranch with defaults 2.0 Pipeline Multibranch Plugin 2.20 Build Pipeline Plugin 1.58 Priority: Major Reporter: Tibor Digana The logs in /job/master/167/console are shown when the build is in progress. After it has finished I see nothing. Only a black narrow bar. The BlueOcen shows me this stacktrace java.io.FileNotFoundException: /var/lib/jenkins/jobs/Invoice/branches/master/builds/166/log (No such file or directory) at java.io.RandomAccessFile.open0(Native Method) at java.io.RandomAccessFile.open(RandomAccessFile.java:316) at java.io.RandomAccessFile.(RandomAccessFile.java:243) at org.jenkinsci.plugins.workflow.log.FileLogStorage.stepLog(FileLogStorage.java:259) at org.jenkinsci.plugins.workflow.support.actions.LogStorageAction.getLogText(LogStorageAction.java:62) at io.jenkins.blueocean.rest.impl.pipeline.PipelineStepImpl.getLog(PipelineStepImpl.java:139) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Nikolas Falco If there are no objections I will introduce XML version in the XSD schema and we will proceed with plugin version 3.0.0-M1. We will have multiple versions of this XML in web deployment and the old versions of plugin would be validated against the old schema. I will open a pull request where you can have a look if you like and this way you will have the result under your control. Is this fair? 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 Tibor Digana edited a comment on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix [~nfalco]Hi Nicolas,Not sure what you mean by??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XMLWith the XML you have to parse whole file and make logic on top to calculate real failures.??As always because this is XML and the stacktrace is not big like kilobytes.Not sure why you validate XML but anyway. Parsing the XML and displaying the statistics is what has to be done by the plugins. In this case we have to find a way how you detect version of the XSD. We have not had any version in the XSD which would be easier to have it in past. What alternatives are you facing in order to detect which XSD is actual?We can fix this as following.I will deploy the old XSD to the old schema location URL="" and I will deploy a new schema location for the current status 2.22.1 with another name of XSD file and new schema location which would have a version 2.22.1. Do you agree or you see another solution?If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. One way or another these Jenkins plugins do not care about Maven plugin versions because they only read the XML report as the outcome of the Maven plugins and Jenkins plugins do not use to check the version of surefire in POM. Not that easy for them. The fact that nobody claimed that the stacktrace contained *std-out* in one string of XML Value means that these features are not much used or the users do not print logs in tested logic on the console, but the frequency of use of these features is more probable. 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 j
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana edited a comment on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix [~nfalco]Hi Nicolas,Not sure what you mean by??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XMLWith the XML you have to parse whole file and make logic on top to calculate real failures.??As always because this is XML and the stacktrace is not big like kilobytes.Not sure why you validate XML but anyway. Parsing the XML and displaying the statistics is what has to be done by the plugins. In this case we have to find a way how you detect version of the XSD. We have not had any version in the XSD which would be easier to have it in past. What alternatives are you facing in order to detect which XSD is actual?We can fix this as following.I will deploy the old XSD to the old schema location URL=""> _ [ https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd _ |https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd] and I will deploy a new schema location for the current status 2.22.1 with another name of XSD file and new schema location which would have a version 2.22.1. Do you agree or you see another solution?If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. One way or another these Jenkins plugins do not care about Maven plugin versions because they only read the XML report as the outcome of the Maven plugins and Jenkins plugins do not use to check the version of surefire in POM. Not that easy for them. The fact that nobody claimed that the stacktrace contained *std-out* in one string of XML Value means that these features are not much used or the users do not print logs in tested logic on the console, but the frequency of use of these features is more probable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- Yo
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana edited a comment on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix [~nfalco]Hi Nicolas,Not sure what you mean by??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XML (not only in console) With the XML you have to parse whole file and make logic on top to calculate real failures.??As always because this is XML and the stacktrace is not big like kilobytes.Not sure why you validate XML but anyway. Parsing the XML and displaying the statistics is what has to be done by the plugins. In this case we have to find a way how you detect version of the XSD. We have not had any version in the XSD which would be easier to have it in past. What alternatives are you facing in order to detect which XSD is actual?We can fix this as following.I will deploy the old XSD to the old schema location URL=""> _https _ https ://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report. xsd_ xsd _ and I will deploy a new schema location for the current status 2.22.1 with another name of XSD file and new schema location which would have a version 2.22.1. Do you agree or you see another solution?If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. One way or another these Jenkins plugins do not care about Maven plugin versions because they only read the XML report as the outcome of the Maven plugins and Jenkins plugins do not use to check the version of surefire in POM. Not that easy for them. The fact that nobody claimed that the stacktrace contained *std-out* in one string of XML Value means that these features are not much used or the users do not print logs in tested logic on the console, but the frequency of use of these features is more probable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed t
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Nikolas Falco Hi Nicolas, Not sure what you mean by ??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XML (not only in console) ?? With the XML you have to parse whole file and make logic on top to calculate real failures. As always because this is XML and the stacktrace is not big like kilobytes. Not sure why you validate XML but anyway. Parsing the XML and displaying the statistics is what has to be done by the plugins. In this case we have to find a way how you detect version of the XSD. We have not had any version in the XSD which would be easier to have it in past. What alternatives are you facing in order to detect which XSD is actual? We can fix this as following. I will deploy the old XSD to the old schema location URL="" href="https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd_" class="external-link" rel="nofollow" style="color: #3b73af; text-decoration: none">https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd_ and I will deploy a new schema location for the current status 2.22.1 with another name of XSD file and new schema location which would have a version 2.22.1. Do you agree or you see another solution? If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. One way or another these Jenkins plugins do not care about Maven plugin versions because they only read the XML report as the outcome of the Maven plugins and Jenkins plugins do not use to check the version of surefire in POM. Not that easy for them. The fact that nobody claimed that the stacktrace contained std-out in one string of XML Value means that these features are not much used or the users do not print logs in tested logic on the console, but the frequency of use of these features is more probable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix I have tried to involve as many plugin as possible in Jenkins and Travis. I saw XUnit related to .Net and not Java. Sorry for that. Mistakes happen the same as developers make mistakes with the XML design regarding elements /flaky and rerun. This is the chance to improve the s/w. Btw we plan to release several release candidates for version 3.0.0 and we will break backwards compatibility in API (not in XML) this time and it is because we have no choice after 15 years. There is time and milestone where we have to say that we have to break something but hopefully not everything. We are not going to create a new plugin but after 15 years it is reasonable. Nikolas, the XML and old XSD was broken. Similar changes happened in Surefire but it was not this schema. It was also with standard output stream which was broken by user's libraries and the error was uncovered in logs however the users do not like it but they had to accept that we also do not want to be responsible for "their" mistakes in their project or used external libraries. 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 Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Oleg Nenashev It seems you agree since you have not reply. I am going to push it to master in ASF Maven. Any objections? 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 Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix These 4 elements are relatively new. Two were missing in XSD but present in XML. As I said bard work on our side. 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 Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix That's the question because for me it breaks the form of report in something (only 4 elements I mentioned above) but the rest remains intact. If you do not mind in the stack trace system-out/err, then you would not see any difference. One way or another it was badly designed XSD/XML which could not be parsed and could not be valid. 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). If they were used in Jenkins plugins and if the XML simple value was observed then it means that your users sometimes observed weird text in stack trace: my console log... 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 Tibor Digana updated an issue Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Tibor Digana Issue Type: Bug Improvement 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 Tibor Digana created an issue Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Issue Type: Bug Assignee: Damian Szczepanik Components: cucumber-reports-plugin, junit-attachments-plugin, junit-plugin, junit-realtime-test-reporter-plugin, testng-plugin Created: 2018-08-25 16:45 Priority: Major Reporter: Tibor Digana I want to inform you that XML Reports of Surefire are not valid against XSD https://github.com/apache/maven-surefire/blob/master/maven-surefire-plugin/src/site/resources/xsd/surefire-test-report.xsd This should be fixed in Maven Surefire. If you use this XML and visualize the reports, pls adapt to the fix. https://issues.apache.org/jira/browse/SUREFIRE-1559 Add Comment
[JIRA] (JENKINS-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana commented on JENKINS-51385 Re: Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Olivier Lamy >> you are using this plugin as well jira-steps-plugin ? I only configured both and do not use it in Jenkinsfile yet. My goal is to have SCM list of changes for the job + build result in a Jira comment. You think that I should disable Jira Steps Plugin? 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-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana commented on JENKINS-51385 Re: Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Olivier Lamy The plugin JIRA Pipeline Steps is installed with latest version 1.4.1. 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-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana commented on JENKINS-51385 Re: Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." I am authenticating with http://10.220.60.167:8080/secure/Dashboard.jspa on Firefox but I know that the admin uses LDAP on Jira server. Did I answer your question? 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-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana commented on JENKINS-51385 Re: Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Although I set it to 3, it is in seconds, I pressed the button "VALIDATE SETTINGS" there is an ERROR after several seconds. 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-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana commented on JENKINS-51385 Re: Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Olivier Lamy Hi Olivier, Would you pls have a look on this issue? I updated the Jira plugin to a new release version according to JENKINS-48357. The build does not hang anymore but I got this issue now. 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-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana updated an issue Jenkins / JENKINS-51385 Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Change By: Tibor Digana My build crashes because Jira plugin times out.In Management page are two sections: JIRA and Jira steps.JIRA nicely connects which is shown on the attachement but the jira steps fails with ERROR.I do not understand the difference but I guess this is the root cause of build failure and the stacktrace in the attachment talks about Jira plugin as well.There is a lot of attachments with screenshots of the job configuration. 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-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana updated an issue Jenkins / JENKINS-51385 Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Change By: Tibor Digana Attachment: management-1.jpg Attachment: management-2.jpg 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-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana updated an issue Jenkins / JENKINS-51385 Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Change By: Tibor Digana Attachment: Jenkinsfile.groovy 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-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana updated an issue Jenkins / JENKINS-51385 Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Change By: Tibor Digana Attachment: JENKINS-51385.jenkins.log Attachment: multibranch-pipeline-job-configuration-1.jpg Attachment: multibranch-pipeline-job-configuration-2.jpg Attachment: multibranch-pipeline-job-configuration-3.jpg 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 receiv
[JIRA] (JENKINS-51385) Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task."
Title: Message Title Tibor Digana created an issue Jenkins / JENKINS-51385 Build crashes after extremely short jira plugin timeout has elapsed "Timeout waiting for task." Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2018-05-17 08:49 Priority: Critical Reporter: Tibor Digana Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you
[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Olivier Lamy Now my build does not hang but I have a new issue with Jira plugin because when I commit with messages which matches a pattern, the Jira plugin times out immediately. Maybe in less than one second. In the Management are two sections: JIRA and JIRA Sites. The first has successful login but the second fails. Why this happens? 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Olivier Lamy Vivek Pandey After I have downgraded Git Client back to 2.7.1 release and still used Olivier's SNAPSHOT of JIRA plugin the build did not hang, hopefully it's fine. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Olivier Lamy Mark Waite I updated both plugins Git Client and JIRA. So it means the change in JIRA was the one which made the build to continue without hanging. The second commit runs as well. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Mark Waite Ok Mark, just ping me when you need my test again. I will try to make few more commits next days on my system. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Olivier Lamy Maybe OSGi would be quite a big deal for the developers. Would it be a generic solution of such problems in all Jenkins plugins? Each Jenkins plugin may have isolated version of JIRA Client and Apache HTTP client. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title
Tibor Digana commented on JENKINS-48357
Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Mark Waite The first commit did not hang and this is the log:
16:11:24 [WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done
[Pipeline] }
[Pipeline] // stage
[Pipeline] echo
16:11:25 shortDescription: Branch indexing
[Pipeline] echo
16:11:25 Job started by timer or branching.
[Pipeline] sh
16:11:25 [ibranch_Pipeline_playground-PRVK7X6T2XH7C3SUJ4JNYHLNG2EVZ6W7C37SOIOU6LWELPYIKHXQ] Running shell script
16:11:25 + mkdir -p build
[Pipeline] dir
16:11:25 Running in /var/lib/jenkins/workspace/ibranch_Pipeline_playground-PRVK7X6T2XH7C3SUJ4JNYHLNG2EVZ6W7C37SOIOU6LWELPYIKHXQ/build
[Pipeline] {
[Pipeline] stage
[Pipeline] { (checkout)
[Pipeline] checkout
16:11:25 Cloning the remote Git repository
16:11:25 Cloning with configured refspecs honoured and without tags
16:11:25 Cloning repository http://git.ads.local/phfa-entervonextgen/audit
16:11:25 > git init /var/lib/jenkins/workspace/ibranch_Pipeline_playground-PRVK7X6T2XH7C3SUJ4JNYHLNG2EVZ6W7C37SOIOU6LWELPYIKHXQ/build # timeout=10
16:11:26 > FINISHED git init /var/lib/jenkins/workspace/ibranch_Pipeline_playground-PRVK7X6T2XH7C3SUJ4JNYHLNG2EVZ6W7C37SOIOU6LWELPYIKHXQ/build # timeout=10
16:11:26 Fetching upstream changes from http://git.ads.local/phfa-entervonextgen/audit
16:11:26 > git --version # timeout=10
16:11:26 > FINISHED git --version # timeout=10
16:11:26 using GIT_ASKPASS to set credentials git private new rsa
16:11:26 > git fetch --no-tags --progress http://git.ads.local/phfa-entervonextgen/audit +refs/heads/*:refs/remotes/origin/*
16:11:30 > FINISHED git fetch --no-tags --progress http://git.ads.local/phfa-entervonextgen/audit +refs/heads/*:refs/remotes/origin/*
16:11:30 > git config remote.origin.url http://git.ads.local/phfa-entervonextgen/audit # timeout=10
16:11:30 > FINISHED git config remote.origin.url http://git.ads.local/phfa-entervonextgen/audit # timeout=10
16:11:30 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
16:11:30 > FINISHED git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
16:11:30 > git config remote.origin.url http://git.ads.local/phfa-entervonextgen/audit # timeout=10
16:11:30 > FINISHED git config remote.origin.url http://git.ads.local/phfa-entervonextgen/audit # timeout=10
16:11:30 Fetching without tags
16:11:30 Fetching upstream changes from http://git.ads.local/phfa-entervonextgen/audit
16:11:30 using GIT_ASKPASS to set credentials git private new rsa
16:11:30 > git fetch --no-tags --progress http://git.ads.local/phfa-entervonextgen/audit +refs/heads/*:refs/remotes/origin/*
16:11:30 > FINISHED git fetch --no-tags --progress http://git.ads.local/phfa-entervonextgen/audit +refs/heads/*:refs/remotes/origin/*
16:11:30 Checking out Revision 512f79c739a04d5001d0c89dc889add0efbf06b9 (playground)
16:11:30 > git config core.sparsecheckout # timeout=10
16:11:30 > FINISHED git config core.sparsecheckout # timeout=10
16:11:30 > git checkout -f 512f79c739a04d5001d0c89dc889add0efbf06b9
16:11:31 > FINISHED git checkout -f 512f79c739a04d5001d0c89dc889add0efbf06b9
16:11:31 Commit message: "Test new Git and JIRA SNAPSHOT plugin with maven-site-plugin:3.7.1"
16:11:31 > git rev-list --no-walk 1535e85a8421d931ea2f54cd26dff47f647ed24b # timeout=10
16:11:31 > FINISHED git rev-list --no-walk 1535e85a8421d931ea2f54cd26dff47f647ed24b # timeout=10
[Pi
[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Mark Waite The link you provided [ git-client-plugin.hpi |https://ci.jenkins.io/job/Plugins/job/git-client-plugin/view/change-requests/job/PR-311/lastSuccessfulBuild/artifact/target/git-client.hpi] is no longer reachable. I want to check it out. Can you create it again pls? I have updated the Jira Plugin from Olivier and I would like to do the same with the Git Plugin. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Mark Waite I have a new findings (yet without your pull request - I will use it soon). The Git plugin hangs on git rev-list --no-walk if the time trigger started the job. It has never been hanged when I triggered manually. Not related to changes in Jenkinsfile as I wrote before. Interesting is that I launched the native commit in WORKSPACE/build which did not hang. Notice that my .git directory is in build directory and not directly in workspace. Not sure why Jenkins and Git plugin calls this command due to it always returns the commit hash itself I used in the command: git rev-list --no-walk 21980ad7f91ab4eb0aeb09b166d66baf7433b7a9 dioes not matter if I checked out the HEAD or some previous commit. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Mark Waite Hi Mark, I found some hint [1] however I use Ubuntu and not Windows, but this forced me to ask you about git credentials and some other question. Maybe the pull request can be extended with some more logs. How credentials are passed to these commands and each of them? Can we see them and is this real command executed in sub-process? Is Git running in a non-interactive mode? Can we detect that Git is interactively asking for some input on STD/IN? I guess Jenkins plugin runs Git in Java sub-process. Can we see std/err as well as std/out in the console including the error code returned by the sub-process? Why timeout 10 minutes is not applied however it is seen in the console log after the command (# timeout=10)? [1]: https://support.cloudbees.com/hc/en-us/articles/221046888-Build-Hang-or-Fail-with-Git-for-Windows 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API I am using Version 2.107.2, restarted of course and using JIRA plugins, all plugins updated. But the git still hangs on this line in logs: 16:25:09 > git rev-list --no-walk 3bb1f0fc92a0cdb29c6df7cd1eb109dbd372929d # timeout=10 Who prints this? The Git or Java? Can you add more debug info? We have to find the root cause. Interesting is that I pushed changes to Jenkinsfile with two commits in the morning. And now in the afternoon I committed Java code. Could it be that Jenkinsfile represents configuration of the job and maybe this behavior (Jenkinsfile -> next commit with some other file(s)) breaks something. Now I have only one possibility to interrupt the build and trigger the build manually. After I did the Jenkins job did not hang. Could it be related to what Jenkinsfile made in job configuration. I don't think it's my fault because I only renamed function isTrunk to isMaster which is easy refactoring. 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-50130) Artifacts are not archived when the build fails using parallel executions.
Title: Message Title Tibor Digana commented on JENKINS-50130 Re: Artifacts are not archived when the build fails using parallel executions. Andrew Bayer Interesting thing is that the archived artifacts appear if the job fails continuously since the beginning. Similar to this: https://builds.apache.org/job/maven-box/job/maven-surefire/job/1512/ I would say that once it becomes blue and then red, the artifacts would not appear in the list of Build Artifacts. 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-50130) Artifacts are not archived when the build fails using parallel executions.
Title: Message Title Tibor Digana commented on JENKINS-50130 Re: Artifacts are not archived when the build fails using parallel executions. Andrew Bayer I also think it is parallelism issue. But what can we do about it? When the Jenkins designer has the code in mind she/he would recognize the issue candidate. Has the function parallel any notion about archivedArtifacts and the setting of the attribute onlyIfSuccessful? 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API I will try to list --global, --local, --system properties in Jenkinsfile and I will compare with my workspace. Next week because now I am on holiday. It's strange to me that Java and Git executable have anything related. Therefore I mentioned env vars because I see only those in common and transaferable. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API I tried to execute exactly the same command by hands and it did not hang. So the case would be that the command displayed in the logs is not exactly identical to the executed one, or the environment variables was added by JIRA plugin. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Michael Neale The influence of JIRA plugin to Git executable would be some environment variable. If you run with/out JIRA plugin, the difference in the environment variables is found. My problem that Git rev-list hangs happens only if I force push to a branch and I push back to master. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API I thought Jenkins was using OSGi and so that plugins run in isolated ClassLoaders. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Michael Neale When this issue will be fixed and why it takes time? 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API ..but which jira plugin to disable? I hope you do not mean MB Pipeline plugin because our company has the biggest benefit from it. 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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title
Tibor Digana edited a comment on JENKINS-48357
Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
[~vivek]Will this really fix https://issues.jenkins-ci.org/browse/JENKINS-43106 ?I have a terrible problem with {{git rev-list}} which hangs on latest Jenkins and Blue Ocean and MB Pipeline. How the Apache client may break cause this native Git (git rev-list) problem if I configured Git Plugin in Jenkins Management to use native Git?
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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title
Tibor Digana edited a comment on JENKINS-48357
Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
[~vivek]Will this really fix https://issues.jenkins-ci.org/browse/JENKINS-43106 ?I ha have a terrible problem with {{ git re rev -list }} which hangs on latest Jenkins and Blue Ocean and MB Pipeline. How the Apache client may break this native Git (git rev-list) problem if I configured Git Plugin in Jenkins Management to use native Git?
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-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Tibor Digana commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Vivek Pandey Will this really fix https://issues.jenkins-ci.org/browse/JENKINS-43106 ? I ha terrible problem with git re-list which hangs on latest Jenkins and Blue Ocean and MB Pipeline. How Apache client may break this native Git (git rev-list) if I configured Git Plugin in Jenkins Management to use native Git? 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-50130) Artifacts are not archived when the build fails using parallel executions.
Title: Message Title
Tibor Digana updated an issue
Jenkins / JENKINS-50130
Artifacts are not archived when the build fails using parallel executions.
Change By:
Tibor Digana
I am calling these functions {{ zip(zipFile: "it--surefire-its--$\{stageKey}.zip", dir: 'surefire-its/target', archive: true) }} {{ archiveArtifacts(artifacts: '*.zip', allowEmptyArchive: true, onlyIfSuccessful: false) }} When the build fails, the artifacts are not available for downloads.If is succeeds, they are available.This is the script [https://github.com/apache/maven-surefire/blob/master/Jenkinsfile]And you can try out this job for instance: [ https://builds.apache.org/job/maven-wip/job/maven-surefire/job/SUREFIRE-1495/ ] I use function {{ parallel() }} as well. Could it be the case?If I use similar script in my company without {{ parallel() }} , the artifacts can be always downloaded.
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 Go
[JIRA] (JENKINS-50130) Artifacts are not archived when the build fails using parallel executions.
Title: Message Title
Tibor Digana created an issue
Jenkins / JENKINS-50130
Artifacts are not archived when the build fails using parallel executions.
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-03-12 19:03
Environment:
Jenkins 2.89.4
Priority:
Major
Reporter:
Tibor Digana
I am calling these functions zip(zipFile: "it-surefire-its-${stageKey}.zip", dir: 'surefire-its/target', archive: true) archiveArtifacts(artifacts: '*.zip', allowEmptyArchive: true, onlyIfSuccessful: false) When the build fails, the artifacts are not available for downloads. If is succeeds, they are available. This is the script https://github.com/apache/maven-surefire/blob/master/Jenkinsfile And you can try out this job for instance: https://builds.apache.org/job/maven-wip/job/maven-surefire/job/SUREFIRE-1495/ I use function parallel() as well. Could it be the case? If I use similar script in my company without parallel(), the artifacts can be always downloaded.
Add Comment
[JIRA] (JENKINS-49614) Function withMaven() fails after Maven process finished normally
Title: Message Title Tibor Digana commented on JENKINS-49614 Re: Function withMaven() fails after Maven process finished normally Stephen Connolly Thx Stephen for a hint. I will take over in Surefire project tomorrow. We are working on a release and this would be part of little improvements. 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-49614) Function withMaven() fails after Maven process finished normally
Title: Message Title Tibor Digana commented on JENKINS-49614 Re: Function withMaven() fails after Maven process finished normally The thing is that the Maven build process, run in the function withMaven(), runs several modules and one of them forks sub-processes which are also Maven native processes. These sub-processes succeed and some just fail which is also expected scenario. I found that one of them sends this text over the Standard Outputstream Std/Out: Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/jenkins/jenkins-slave/workspace/n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp/withMavenba69d9b6/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/jenkins/jenkins-slave/workspace/n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp/withMavenba69d9b6" This is maybe interesting for you. Altogether the last module forks 750 sub-processes and waiting until all have finished. Not sure what you do with our Maven run. It looks to me a kind of proxy around them. Additionally we have tests which are expected to call a native library which should cause segfault and this text comes from the stream out. It looks to me that all the analysis goes through all the integration tests unexpectedly. If the function openTasksPublisher() was enabled, I could not read Jenkins page because of 100 identical reports. So I disabled it, but I can see that all 5 publishers print "skipping..." with tons of logs and maybe there is the cause of InterruptedException. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You recei
[JIRA] (JENKINS-49614) Function withMaven() fails after Maven process finished normally
Title: Message Title
Tibor Digana updated an issue
Jenkins / JENKINS-49614
Function withMaven() fails after Maven process finished normally
Change By:
Tibor Digana
Cyrille, I guess StephenC meant you on our Maven mailing list.So I assigned this issue to you.Within the function *withMaven()* I disabled all publishers because they were duplicated, maybe 100 identical reports. The function takes some time to continue after Maven run has finished and then suddenly tons of logs is printed saying that *** publisher is disabled, etc. In the logs the exception {{InterruptedException}} is thrown and then the logs continue. My main problem is this error:(a copy taken from the ASF mailing list) I have got BUILD SUCCESS of Maven run but the function *withMaven()* fails right after the Maven process has finished. I have no idea why.Because of this call in the stacktrace*WithMavenStepExecution$WorkspaceCleanupCallback.finished*I guess the function *withMaven()* is still doing something much later when *cleanWs()* finished.The principle looks like this:*try \{* *withMaven()**} finally \{* *cleanWs()* *}*This is the stacktrace:[windows] [INFO] BUILD SUCCESS [windows] [INFO] [windows] [INFO] Total time: 43:08 min [windows] [INFO] Finished at: 2018-02-18T04:34:10+00:00 [windows] [INFO] Final Memory: 48M/161M [windows] [INFO] [windows] [INFO] [jenkins-event-spy] Generated F:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\maven-spy-20180218-035101-1877982869374894449694.log [windows] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f" [Pipeline] [windows] } [windows] ERROR: [withMaven] WARNING Exception processing the logs generated by the Jenkins Maven Event Spy f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\maven-spy-20180218-042026-3958838718902276550716.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org [windows] java.lang.InterruptedException [windows] at java.lang.Object.wait(Native Method) [windows] at hudson.remoting.Request.call(Request.java:167) [windows] at hudson.remoting.Channel.call(Channel.java:907) [windows] at hudson.FilePath.act(FilePath.java:986) [windows] at hudson.FilePath.act(FilePath.java:975) [windows] at hudson.FilePath.exists(FilePath.java:1440) [windows] at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogP
[JIRA] (JENKINS-49614) Function withMaven() fails after Maven process finished normally
Title: Message Title
Tibor Digana updated an issue
Jenkins / JENKINS-49614
Function withMaven() fails after Maven process finished normally
Change By:
Tibor Digana
Cyrille, I guess StephenC meant you on our Maven mailing list.So I assigned this issue to you.Within the function *withMaven()* I disabled all publishers because they were duplicated, maybe 100 identical reports. The function takes some time to continue after Maven run has finished and then suddenly tons of logs is printed saying that *** publisher is disabled, etc. My main problem is this error:( paste a copy taken from the ASF mailing list) I have got BUILD SUCCESS of Maven run but the function *withMaven()* fails right after the Maven process has finished. I have no idea why.Because of this call in the stacktrace*WithMavenStepExecution$WorkspaceCleanupCallback.finished*I guess the function *withMaven()* is still doing something much later when *cleanWs()* finished.The principle looks like this:*try \{* *withMaven()**} finally \{* *cleanWs()**}* This is the stacktrace:[windows] [INFO] BUILD SUCCESS[windows] [INFO] [windows] [INFO] Total time: 43:08 min[windows] [INFO] Finished at: 2018-02-18T04:34:10+00:00[windows] [INFO] Final Memory: 48M/161M[windows] [INFO] [windows] [INFO] [jenkins-event-spy] Generated F:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\maven-spy-20180218-035101-1877982869374894449694.log[windows] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f" [Pipeline] [windows] }[windows] ERROR: [withMaven] WARNING Exception processing the logs generated by the Jenkins Maven Event Spy f:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\maven-spy-20180218-042026-3958838718902276550716.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org [windows] java.lang.InterruptedException[windows] at java.lang.Object.wait(Native Method)[windows] at hudson.remoting.Request.call(Request.java:167)[windows] at hudson.remoting.Channel.call(Channel.java:907)[windows] at hudson.FilePath.act(FilePath.java:986)[windows] at hudson.FilePath.act(FilePath.java:975)[windows] at hudson.FilePath.exists(FilePath.java:1440)[windows] at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:105)[windows] at org.jenkinsci.plugins.pip
[JIRA] (JENKINS-49614) Function withMaven() fails after Maven process finished normally
Title: Message Title
Tibor Digana created an issue
Jenkins / JENKINS-49614
Function withMaven() fails after Maven process finished normally
Issue Type:
Bug
Assignee:
Cyrille Le Clerc
Components:
pipeline-maven-plugin
Created:
2018-02-18 17:35
Environment:
Apache Jenkins CI, Windows NT slave
Priority:
Major
Reporter:
Tibor Digana
Cyrille, I guess StephenC meant you on our Maven mailing list. So I assigned this issue to you. Within the function withMaven() I disabled all publishers because they were duplicated, maybe 100 identical reports. The function takes some time to continue after Maven run has finished and then suddenly tons of logs is printed saying that *** publisher is disabled, etc. My main problem is this error: (paste from the ASF mailing list) I have got BUILD SUCCESS of Maven run but the function withMaven() fails right after the Maven process has finished. I have no idea why.Because of this call in the stacktrace WithMavenStepExecution$WorkspaceCleanupCallback.finished I guess the function withMaven() is still doing something much later when cleanWs() finished. The principle looks like this: try { withMaven()} finally { cleanWs() } This is the stacktrace: [windows] [INFO] BUILD SUCCESS [windows] [INFO] [windows] [INFO] Total time: 43:08 min [windows] [INFO] Finished at: 2018-02-18T04:34:10+00:00 [windows] [INFO] Final Memory: 48M/161M [windows] [INFO] [windows] [INFO] [jenkins-event-spy] Generated F:\jenkins\jenkins-slave\workspace\n-wip_maven-surefire_master-VMXNEFVLKSG4Y4Q25OS6RZDPHGE56CJURNETLF6TR2V5RXK7KNVQ@tmp\withMavene898fc1f\maven-spy-20180218-035101-1877982869374894449694.log [windows] Picke
[JIRA] [jacoco-plugin] (JENKINS-25076) Jenkins Jacoco plugin shows 0% branch coverage when jacoco report shows n/a
Title: Message Title Tibor Digana commented on JENKINS-25076 Re: Jenkins Jacoco plugin shows 0% branch coverage when jacoco report shows n/a Jeremy Brown Jeremy Brown I had the same problem when I built jacoco.exe with Maven plugin version 0.7.5 however Jankins JaCoCo plugin version was 1.0.x. The versions 1.0.x should use Maven plugin version 0.7.4 or lower. After my admin did upgrade of Jenkins plugin to version 2.0.0 the problem disappeared with Maven plugin version 0.7.5.. Although the graph is displayed I found another issue JENKINS-32528. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jacoco-plugin] (JENKINS-32528) Jenkins JaCoCo Plugin 2.0.0 shows HTML code in Coverage Trend
Title: Message Title Tibor Digana created an issue Jenkins / JENKINS-32528 Jenkins JaCoCo Plugin 2.0.0 shows HTML code in Coverage Trend Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 20/Jan/16 9:18 AM Environment: Jenkins 1.609.3 Labels: plugin user-experience jenkins plugins Priority: Critical Reporter: Tibor Digana In POM I am using version latest 0.7.5. In Jenkins we use the latest JaCoCo plugin 2.0.0. Actual: We restarted the Jenkins and the last build shows this HTML code https://builds.apache.org/job/maven-surefire/lastBuild/jacoco/ Expected: The Coverage page shows JaCoCo table in browser and not the code of the table.
