[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs

[clecl...@cloudbees.com (JIRA)]

Title: Message Title

Cyrille Le Clerc commented on JENKINS-49337   Re: InterruptedException - Exception processing the logs https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/master/1211 > Regarding fingerprinting I'm keeping since I think it's necessary to perform automatic trigger or downstream jobs. This is the comment I had put in the XWiki pipeline job at https://github.com/xwiki/xwiki-jenkins-pipeline/blob/d0b2330b1cedad2f2a38b3eb575cc7c81d4d0bdd/vars/xwikiBuild.groovy#L61 : > // fingerprintDependencies = false (default to true since it's required by the withMaven dependency graph feature > // in order to have builds trigger automatically other builds when dependencies are built) > Could you confirm that it's correct? Fingerprinting is NOT required to trigger downstream pipelines. The "Pipeline Graph Publisher" is self sufficient and does not need any other publisher. It works on the semantic dependencies between Maven artifacts to trigger downstream pipelines > I assume you're referring to some try/catch you have in Jenkins's code. Let me know when some new version is available and I'll upgrade. Correct, improvement of the try/catch in the plugin https://ci.xwiki.org/job/XWiki/job/xwiki-platform/job/master/1211 [withMaven] Publishers: Invoker Publisher: 20 ms, Junit Publisher: 18273 ms, Concordion Publisher: 4 ms, Dependencies Fingerprint Publisher: 115889 ms, Findbugs Publisher: 3 ms, JGiven Publisher: 24 ms, Jacoco Publisher: 3 ms, Pipeline Graph Publisher: 797 ms, SpotBugs Publisher: 3 ms, Open Task Scanner Publisher: 13 ms [withMaven] Publishers: Dependencies Fingerprint Publisher: 5 ms, JGiven Publisher: 1 ms, Pipeline Graph Publisher: 2 ms, Open Task Scanner Publisher: 14 ms [withMaven] Publishers: Junit Publisher: 5753 ms, Dependencies Fingerprint Publisher: 2941 ms, Pipeline Graph Publisher: 17 ms, Open Task Scanner Publisher: 18 ms [withMaven] Publishers: Junit Publisher: 3718 ms, Dependencies Fingerprint Publisher: 14 ms, JGiven Publisher: 3 ms, Pipeline Graph Publisher: 10 ms, Open Task Scanner Publisher: 17 ms [withMaven] Publishers: Junit Publisher: 8112 ms, Dependencies Fingerprint Publisher: 6 ms, Pipeline Graph Publisher: 4 ms, Open Task Scanner Publisher: 15 ms [withMaven] Publishers: Junit Publisher: 115970 ms, Dependencies Fingerprint Publisher: 385 ms, JGiven Publisher: 24 ms, Pipeline Graph Publisher: 3 ms, Open Task Scanner Publisher: 102 ms [withMaven] Publishers: Junit Publisher: 152231 ms, Dependencies Fingerprint Publisher: 317 ms, Pipeline Graph Publisher: 7 ms, Open Task Scanner Publisher: 223 ms [withMaven] Publishers: Junit Publisher: 4669 ms, Dependencies Fingerprint Publisher: 1585 ms, Pipeline Graph Publisher: 13 ms, Open Task Scanner Publisher: 19 ms [withMaven] Publishers: Invoker Publisher: 1 ms, Junit Publisher: 8472 ms, Dependencies Fingerprint Publisher: 27 ms, JGiven Publisher: 7 ms, Pipeline Graph Publisher: 12 ms, Open Task Scanner Publisher: 18 ms [withMaven] Publishers: Junit Publisher: 11656 ms, Dependencies Fingerprint Publisher: 585 ms, Pipeline Graph Publisher: 2 ms, Open Task Scanner Publisher: 7 ms The pipeline seems to have run without any problem caused by withMaven 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.