[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title
Alex V updated an issue
Jenkins / JENKINS-60193
NPE in JabberPublisherDescriptor in new install
Change By:
Alex V
* Create a docker image with the following docker file:{ { noformat} FROM jenkins/jenkins:lts}}{{RUN /usr/local/bin/install-plugins.sh \ }} {{ active-directory \ }} {{ build-failure-analyzer \ }} {{ claim \ }} {{ configuration-as-code \ }} {{ credentials-binding \ }} {{ docker-workflow \ }} {{ email-ext \ }} {{ gitlab-branch-source \ }} {{ jabber \ }} {{ ldap \ }} {{ lockable-resources \ }} {{ pipeline-stage-view \ }} {{ rebuild \ }} {{ role-strategy \ }} {{ ssh-slaves {noformat } } * It creates an image with the following versions{ { noformat} Installed plugins: }} {{ ace-editor:1.1 }} {{ active-directory:2.16 }} {{ apache-httpcomponents-client-4-api:4.5.10-2.0 }} {{ authentication-tokens:1.3 }} {{ branch-api:2.5.4 }} {{ build-failure-analyzer:1.24.1 }} {{ claim:2.16 }} {{ cloudbees-folder:6.9 }} {{ configuration-as-code:1.33 }} {{ credentials-binding:1.20 }} {{ credentials:2.3.0 }} {{ display-url-api:2.3.2 }} {{ docker-commons:1.15 }} {{ docker-workflow:1.21 }} {{ durable-task:1.33 }} {{ email-ext:2.68 }} {{ git-client:3.0.0 }} {{ git:4.0.0 }} {{ gitlab-api:1.0.5 }} {{ gitlab-branch-source:1.4.0 }} {{ handlebars:1.1.1 }} {{ instant-messaging:1.38 }} {{ jabber:1.38 }} {{ jackson2-api:2.10.0 }} {{ javadoc:1.5 }} {{ jquery-detached:1.2.1 }} {{ jsch:0.1.55.1 }} {{ junit:1.28 }} {{ ldap:1.21 }} {{ lockable-resources:2.7 }} {{ mailer:1.29 }} {{ matrix-auth:2.5 }} {{ matrix-project:1.14 }} {{ maven-plugin:3.4 }} {{ momentjs:1.1.1 }} {{ pipeline-graph-analysis:1.10 }} {{ pipeline-input-step:2.11 }} {{ pipeline-rest-api:2.12 }} {{ pipeline-stage-step:2.3 }} {{ pipeline-stage-view:2.12 }} {{ plain-credentials:1.5 }} {{ rebuild:1.31 }} {{ role-strategy:2.15 }} {{ scm-api:2.6.3 }} {{ script-security:1.67 }} {{ ssh-credentials:1.18 }} {{ ssh-slaves:1.31.0 }} {{ structs:1.20 }} {{ token-macro:2.10 }} {{ trilead-api:1.0.5 }} {{ workflow-api:2.37 }} {{ workflow-basic-steps:2.18 }} {{ workflow-cps:2.76 }} {{ workflow-durable-task-step:2.35 }} {{ workflow-job:2.36 }} {{ workflow-scm-step:2.9 }} {{ workflow-step-api:2.20 }} {{ workflow-support:3.3 {noformat } }* Start the container and go to localhost:8080/configureGUI seems normal, with Enable jabber notifications not checked: OKseveral exceptions appears in logs (see attached file): not OK. {{ NPE extract: }} { { noformat} 2019-11-18 08:52:28.455+ [id=80] WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: instance.proxyTypeString==value in /configure. Reason: java.lang.reflect.InvocationTargetException }} {{ java.lang.NullPointerException }} {{ at hudson.plugins.jabber.im.transport.JabberPublisherDescriptor.getProxyTypeString(JabberPublisherDescriptor.java:500) }} {{ Caused: java.lang.reflect.InvocationTargetException }} {{ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title
Alex V created an issue
Jenkins / JENKINS-60193
NPE in JabberPublisherDescriptor in new install
Issue Type:
Bug
Assignee:
Florian Schmaus
Attachments:
jenkins.log
Components:
jabber-plugin
Created:
2019-11-18 08:57
Environment:
Jenkins ver. 2.190.2 jabber:1.38
Priority:
Minor
Reporter:
Alex V
Create a docker image with the following docker file:
FROM jenkins/jenkins:lts{{RUN /usr/local/bin/install-plugins.sh }} {{ active-directory }} {{ build-failure-analyzer }} {{ claim }} {{ configuration-as-code }} {{ credentials-binding }} {{ docker-workflow }} {{ email-ext }} {{ gitlab-branch-source }} {{ jabber }} {{ ldap }} {{ lockable-resources }} {{ pipeline-stage-view }} {{ rebuild }} {{ role-strategy }} {{ ssh-slaves}}
It creates an image with the following versions
Installed plugins: ace-editor:1.1 active-directory:2.16 apache-httpcomponents-client-4-api:4.5.10-2.0 authentication-tokens:1.3 branch-api:2.5.4 build-failure-analyzer:1.24.1 claim:2.16 cloudbees-folder:6.9 configuration-as-code:1.33 credentials-binding:1.20 credentials:2.3.0 display-url-api:2.3.2 docker-commons:1.15 docker-workflow:1.21 durable-task:1.33 email-ext:2.68 git-client:3.0.0 git:4.0.0 gitlab-api:1.0.5
[JIRA] (JENKINS-42946) NPE in CircularStabilityHistory.
Title: Message Title Alex V updated an issue Jenkins / JENKINS-42946 NPE in CircularStabilityHistory. Change By: Alex V Environment: jenkins: 2. 50 51 (ran directly)test-stabillity-plugin 2.2master: debian 8 64 bits / oracle jdk 1.8.0_66slaves: debian 8 64 bits in a docker container on various ubuntu 14.04/64bits machines (with oracle jdk 1.8.0_111) 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-42946) NPE in CircularStabilityHistory.
Title: Message Title Alex V created an issue Jenkins / JENKINS-42946 NPE in CircularStabilityHistory. Issue Type: Bug Assignee: kutzi Components: test-stability-plugin Created: 2017/Mar/20 5:16 PM Environment: jenkins: 2.50 (ran directly) test-stabillity-plugin 2.2 master: debian 8 64 bits / oracle jdk 1.8.0_66 slaves: debian 8 64 bits in a docker container on various ubuntu 14.04/64bits machines (with oracle jdk 1.8.0_111) Priority: Major Reporter: Alex V Whenever a job has failing tests, those failing tests are not shown in jenkins and the following error happens. ERROR: Step ‘Publier le rapport des résultats des tests JUnit’ aborted due to exception: java.lang.NullPointerException at java.lang.Class.isAssignableFrom(Native Method) at de.esailors.jenkins.teststability.CircularStabilityHistory$ConverterImpl.canConvert(CircularStabilityHistory.java:98) at com.thoughtworks.xstream.core.DefaultConverterLookup.registerConverter(DefaultConverterLookup.java:74) at com.thoughtworks.xstream.XStream$2.registerConverter(XStream.java:502) at com.thoughtworks.xstream.XStream.registerConverter(XStream.java:1422) at com.thoughtworks.xstream.XStream.registerConverter(XStream.java:1417) at de.esailors.jenkins.teststability.CircularStabilityHistory.(CircularStabilityHistory.java:92) Caused: java.lang.ExceptionInInitializerError at de.esailors.jenkins.teststability.StabilityTestDataPublisher.contributeTestData(StabilityTestDataPublisher.java:98) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:183) at
[JIRA] [junit-plugin] (JENKINS-27931) stdout/stderr are truncated even on failing test
Alex V
updated JENKINS-27931
stdout/stderr are truncated even on failing test
Change By:
Alex V
(14/Apr/15 1:49 PM)
Description:
Atestclasswithmanytestsinitmayproducelargelogsonstdout.Inthatcase,ifthereisatestfailingwithinthistestclass,Iwouldhaveexpectedthattheentirestdoutoutputiskeptbyjunitplugin.Butitistruncated.{code}...[truncated1051034chars]...{code}Thisseemstobevoluntary:https://github.com/jenkinsci/junit-plugin/commit/5f7513baff89516cd7217ea39101ad67116cd059Itotallyunderstandtheneedofdiscarddatafortestssucceed.Howeverforfailingtests,itmakesalmostimpossibletofindthecauseoffailure.Besides,itcontradictsthedocumentationoftheoption{{Retainlongstandardoutput/error}}whichstates:{panel}Ifchecked,anystandardoutputorerrorfromatestsuitewillberetainedinthetestresultsafterthebuildcompletes.(Thisrefersonlytoadditionalmessagesprintedtoconsole,nottoafailurestacktrace.){color:red}Suchoutputisalwayskeptifthetestfailed{color},butbydefaultlengthyoutputfrompassingtestsistruncatedtosavespace.Checkthisoptionifyouneedtoseeeverylogmessagefromevenpassingtests,butbewarethatJenkinssmemoryconsumptioncansubstantiallyincreaseasaresult,evenifyouneverlookatthetestresults!{panel}Isthatpossibletoatleastmakethisconfigurable
.
?
Inmyworkflow,theidealwouldbetocompletelydiscardpassingtestslogs,andkeepalloffailingones.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-27931) stdout/stderr are truncated even on failing test
Alex V created JENKINS-27931 stdout/stderr are truncated even on failing test Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 14/Apr/15 1:48 PM Description: A test class with many tests in it may produce "large" logs on stdout. In that case, if there is a test failing within this test class, I would have expected that the entire stdout output is kept by junit plugin. But it is truncated. ...[truncated 1051034 chars]... This seems to be voluntary: https://github.com/jenkinsci/junit-plugin/commit/5f7513baff89516cd7217ea39101ad67116cd059 I totally understand the need of discard data for tests succeed. However for failing tests, it makes almost impossible to find the cause of failure. Besides, it contradicts the documentation of the option Retain long standard output/error which states: If checked, any standard output or error from a test suite will be retained in the test results after the build completes. (This refers only to additional messages printed to console, not to a failure stack trace.) Such output is always kept if the test failed, but by default lengthy output from passing tests is truncated to save space. Check this option if you need to see every log message from even passing tests, but beware that Jenkins's memory consumption can substantially increase as a result, even if you never look at the test results! Is that possible to at least make this configurable. In my workflow, the ideal would be to completely discard passing tests logs, and keep all of failing ones. Environment: Jenkins 1.609 Junit plugin 1.5 Project: Jenkins Labels: stdout truncation Priority: Major Reporter: Alex V This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
