[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner edited a comment on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page I just checked it with our second jenkins instance:# stacktrace (same as listed in the description) when opening /manage in 2.215 using locale DE# switching to EN and opening /manage: no stacktrace# switching back to DE: stacktrace again# switching to EN and opening /manage: no stacktrace# starting update to 2.217 without automtic restart# waiting until download/preinstall is complete# switching to DE and opening /manage: no stacktrace# restart# running 2 . .. 217, using DE and opening /manage: no stacktrace 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.204185.1579678665000.4833.1579858860377%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner edited a comment on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page I just checked it with our second jenkins instance:# stacktrace (same as listed in the description) when opening /manage in 2.215 using locale DE (x) # switching to EN and opening /manage: no stacktrace (/) # switching back to DE: stacktrace again (x) # switching to EN and opening /manage: no stacktrace (/) # starting update to 2.217 without automtic automatic restart# waiting until download/preinstall is complete# switching to DE and opening /manage: no stacktrace (/) # restart# running 2.217, using DE and opening /manage: no stacktrace (/) 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.204185.1579678665000.4834.1579858860399%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner edited a comment on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page I just checked it with our second jenkins instance:# stacktrace (same as listed in the description) when opening /manage in 2.215 using locale DE# switching to EN and opening /manage: no stacktrace# switching back to DE: stacktrace again# switching to EN and opening /manage: no stacktrace# starting update to 2.217 without automtic restart# waiting until download/preinstall is complete# restart# ...# switching to DE and opening /manage: no stacktrace # restart# ... 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.204185.1579678665000.4830.1579858740265%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner edited a comment on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page I just checked it with our second jenkins instance:# stacktrace (same as listed in the description) when opening /manage in 2.215 using locale DE# switching to EN and opening /manage: no stacktrace# switching back to DE: stacktrace again# switching to EN and opening /manage: no stacktrace# starting update to 2.217 without automtic restart# waiting until download/preinstall is complete# restart# ...# switching to DE and opening /manage: no stacktrace 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.204185.1579678665000.4827.1579858740220%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner commented on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page I just checked it with our second jenkins instance: stacktrace (same as listed in the description) when opening /manage in 2.215 using locale DE switching to EN and opening /manage: no stacktrace switching back to DE: stacktrace again switching to EN and opening /manage: no stacktrace starting update to 2.217 without automtic restart waiting until download/preinstall is complete switching to DE and opening /manage: no stacktrace 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.204185.1579678665000.4824.1579858680161%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner commented on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page Unfortunalty I can confirm this: I just did my daily update check an opened our jenkins /manage (still using DE loacle and version 2.215) an got again an Exception Stacktrace. Switching to EN did it again and I was able to start the automatic update to 2.217 Due to running jobs the update restart of jenkins is delayed and I was curious if the stacktrace was the same as listed in the description, so I switched back to DE and opened /manage again To my suprise no stacktrace this time (still version 2.215)! Let's wait an see what happens when 2.217 is up ... 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.204185.1579678665000.4817.1579858320396%40Atlassian.JIRA.
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title Norbert Pfistner edited a comment on JENKINS-54596 Re: can't parse argument number: changelog.url Same to mee me after upgrading to 2.214 but I solved it by# forcing english locale (using Quick Locale Switcher in FF)# opening manage page (now works fine when in EN)# updating to Jenkins ver. 2.215In Jenkins ver. 2.215 seems to fix the Issue; switching back to DE locale and opening manage page works fine now 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.195383.1542102275000.3642.1579680661205%40Atlassian.JIRA.
[JIRA] (JENKINS-54596) can't parse argument number: changelog.url
Title: Message Title Norbert Pfistner commented on JENKINS-54596 Re: can't parse argument number: changelog.url Same to mee but I solved it by forcing english locale (using Quick Locale Switcher in FF) opening manage page (now works fine when in EN) updating to Jenkins ver. 2.215 In Jenkins ver. 2.215 seems to fix the Issue; switching back to DE locale and opening manage page works fine now 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.195383.1542102275000.3617.1579680360538%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner edited a comment on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page Solved by# forcing english locale (using Quick Locale Switcher in FF)# opening manage page (now works fine when in EN)# updating to Jenkins ver. 2.215In Jenkins ver. 2.215 seems to fix the Issue; switching back to DE locale and opening manage page works fine now 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.204185.1579678665000.3614.1579680360294%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner commented on JENKINS-60834 Re: Stacktrace when opening jenkins maintenance page Solved by forcing english locale (using Quick Locale Switcher in FF) opening manage page (now works fine when in EN) updating to Jenkins ver. 2.215 In Jenkins ver. 2.215 seems to fix the Issue; switching back to DE locale and opening manage page works fine now 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.204185.1579678665000.3613.1579680300053%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title
Norbert Pfistner updated an issue
Jenkins / JENKINS-60834
Stacktrace when opening jenkins maintenance page
Change By:
Norbert Pfistner
When i click on "Jenkins verwalten" instead of displaying possible updates the page shows the following stacktrace ; so i'm not abnle to update or revert any update i recently made : {noformat}Stack-Traceorg.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.214.jar!/hudson/model/UpdateCenter/CoreUpdateMonitor/message.jelly:53:20: can't parse argument number: changelog.url at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner updated an issue Jenkins / JENKINS-60834 Stacktrace when opening jenkins maintenance page Change By: Norbert Pfistner Priority: Minor Blocker 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.204185.1579678665000.3580.1579678740089%40Atlassian.JIRA.
[JIRA] (JENKINS-60834) Stacktrace when opening jenkins maintenance page
Title: Message Title Norbert Pfistner created an issue Jenkins / JENKINS-60834 Stacktrace when opening jenkins maintenance page Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2020-01-22 07:37 Environment: Erstelldatum dieser Seite: 22.01.2020 08:29:14 MEZ REST API Jenkins ver. 2.214 Priority: Minor Reporter: Norbert Pfistner When i click on "Jenkins verwalten" instead of displaying possible updates the page shows the following stacktrace: Stack-Trace org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.214.jar!/hudson/model/UpdateCenter/CoreUpdateMonitor/message.jelly:53:20: can't parse argument number: changelog.url at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commo
[JIRA] (JENKINS-54713) UI Exception after upgraden plugins
Title: Message Title Norbert Pfistner commented on JENKINS-54713 Re: UI Exception after upgraden plugins Reverting the ssh-slaves plugin did the job! Many thanks! You saved my day! 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-54713) UI Exception after upgraden plugins
Title: Message Title
Norbert Pfistner updated an issue
Jenkins / JENKINS-54713
UI Exception after upgraden plugins
Change By:
Norbert Pfistner
After updating some plugins jenkins ui is rendered unusable.It shows very shorty the expacted page but the switches to a broken page only showing some kind of stacktrace/broken page mixture. The same stacktrace is also in the logfile:{noformat}Caused by: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/Base64at hudson.plugins.translation.L10nDecorator.encodeRecording(L10nDecorator.java:97)at sun.reflect.GeneratedMethodAccessor222.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24)at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)... 72 more{noformat} The plugins I updated should be the following ones:{noformat}ls -lrt jenkins/plugins-rw-r--r-- 1 281390 20. Nov 07:26 branch-api.jpi-rw-r--r-- 1 51513 20. Nov 07:26 durable-task.jpi-rw-r--r-- 1 215545 20. Nov 07:26 cloudbees-folder.jpi-rw-r--r-- 1 2599005 20. Nov 07:26 git-client.jpi-rw-r--r-- 1 385003 20. Nov 07:26 trilead-api.jpi-rw-r--r-- 1 104090 20. Nov 07:26 ssh-slaves.jpi-rw-r--r-- 1 26561 20. Nov 07:26 display-url-api.jpi-rw-r--r-- 1 154949 20. Nov 07:26 workflow-api.jpi-rw-r--r-- 1 19109 20. Nov 07:26 pipeline-graph-analysis.jpidrwxr-xr-x 4 4096 20. Nov 07:27 trilead-apidrwxr-xr-x 4 4096 20. Nov 07:27 git-clientdrwxr-xr-x 4 4096 20. Nov 07:27 workflow-apidrwxr-xr-x 5 4096 20. Nov 07:27 cloudbees-folderdrwxr-xr-x 4 4096 20. Nov 07:27 pipeli
[JIRA] (JENKINS-54713) UI Exception after upgraden plugins
Title: Message Title Norbert Pfistner created an issue Jenkins / JENKINS-54713 UI Exception after upgraden plugins Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: trilead-api-plugin Created: 2018-11-20 07:40 Environment: Jenkins ver. 2.151 Priority: Blocker Reporter: Norbert Pfistner After updating some plugins jenkins ui is rendered unusable. It shows very shorty the expacted page but the switches to a broken page only showing some kind of stacktrace/broken page mixture. The same stacktrace is also in the logfile: Caused by: java.lang.NoClassDefFoundError: com/trilead/ssh2/crypto/Base64 at hudson.plugins.translation.L10nDecorator.encodeRecording(L10nDecorator.java:97) at sun.reflect.GeneratedMethodAccessor222.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.Escapin
[JIRA] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Norbert Pfistner
created JENKINS-21842
Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
security
Created:
18/Feb/14 9:14 AM
Description:
Since the latest update to 1.551 none of our jenkins URLS are displayed in our JIRA Wallboard (using custom web page Gadget). The portion of the Wallboard is simply blank. Technically the JARI gagdet only inserts the pages by using an iframe. The URL is correct, but the page ist not displayed due to an HTML Option added in 1.551:
{
}
Release Notes of 1.551:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-02-14
SECURITY-80 is resaponsible for the change
This is the commit which introduced the new behaviour:
https://github.com/jenkinsci/jenkins/commit/16931bd7bf7560e26ef98328b8e95e803d0e90f6
Yes the changes enhance the security, but both our JIRA and our JENKINS access is limited to our company LAN.
So we would recommend to add a security configuration setting for this to allow the usage of the jenkins pages within other Pages (e.g. JIRA Wallboards).
Project:
Jenkins
Priority:
Major
Reporter:
Norbert Pfistner
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Norbert Pfistner commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ I can also confirm that this is fixed in 1.547 Many thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Norbert Pfistner commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ The effected versions are 1.545 and 1.546 so far. Switching back to version 1.544 fixes the bug but is for sure no suitable solution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Norbert Pfistner created JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ Issue Type: Bug Assignee: vjuranek Attachments: selenium_firefox Config [Jenkins] - Mozilla Firefox_2014-01-07_09-24-03.png Components: build-publisher Created: 07/Jan/14 8:26 AM Description: We have a job which triggers three other jobs and aggregates their test results using post build actions: Aggregate post build test results (german: "Nachgelagerte Testergebnisse zusammenfassen") [x] Aggregate all post build jobs [x] Aggregate failed build result Build jobs (german: "Weitere Projekte bauen") [x] trigger only on build success [ ] trigger even when build is instable [ ] trigger even when build fails When starting this job it fails quickly with an NullPointer exception: Started by user anonymous Building in workspace /ps/devop/jenkins/data/jobs/selenium_firefox/workspace ERROR: Publisher hudson.tasks.test.AggregatedTestResultPublisher aborted due to exception java.lang.NullPointerException at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.getProject(AggregatedTestResultPublisher.java:173) at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.(AggregatedTestResultPublisher.java:146) at hudson.tasks.test.AggregatedTestResultPublisher$TestResultAction.(AggregatedTestResultPublisher.java:135) at hudson.tasks.test.AggregatedTestResultPublisher.perform(AggregatedTestResultPublisher.java:90) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Finished: FAILURE The aggregation is crucial for our dashboard which displays the overall testresults history chart. P.S.: Sorry, I only use the german translation, so I just guessed the actual english configuration lables above. Project: Jenkins Priority: Blocker Reporter: Norbert Pfistner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Norbert Pfistner commented on JENKINS-20630 Jenkins fails to start Same to me after upgrade from 1.539 to 1.540 on Windows7 x64 I started the update by using the jenkins->configure system->automatically update feature on our runing instance. First time in several years the upgraded release is broken ... I now reverted back to 1.539 I'd like to provide a wish list concerning this bug: fix the bug home page link stable releases and label it as stable link weekly builds and label them clearly as at your own risk jenkins->configure system->update link stable release only This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
