[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Raphael Greger commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 As I read, the violations plugin will be replaced by the warnings plugin. So I removed the violations plugin and my Jenkins is now running without 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Raphael Greger commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Thank you for your answer, but in my case it do not solve the problem. I restarted Jenkins the last 3 days more than 20 times. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Mattsi Jansky commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 In our case, we found that (for whatever reason) restarting the Jenkins instance fixed the issue. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Raphael Greger commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have this issue on new updated Jenkins (2.138.3). I can't create or open a Jenkins job with Maven type. It tries to load the config page and the loading symbol do not stop moving. If I remove the mentioned "violations" plugin, it works again. But I can't just remove the plugin. It will be needed for the code analysis I guess. Are there any news? 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Jesse Glick commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 This issue seems to have become a grab-bag of possibly many unrelated problems, without steps to reproduce. I would suggest closing it. Anyone encountering reproducible issues should please ignore this and file fresh issues with complete steps to reproduce from scratch. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Mattsi Jansky commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Having this issue on a brand new Jenkins ver. 2.138.1 instance with only the default suggested plugins, can't create a new build pipeline because of it. Don't have violations plugin. Can't remove the credentials plugin because everything (even git integration) is dependent on it. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Jorge Matricali commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Deactivating Violations plugin just works. Thank you 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Lambert Ma commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Deactivating just Violations plugin 0.7.11 work for us. Using Jenkins 2.107.2 LTS also. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Marin Binzari commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Same here with Jenkins 2.107.2. Desactivating the Violations plugin 0.7.11 (with dependencies on him Violation Columns(List View Columns) 1.6, Warnings Plug-in, Static Analysis Collector Plug-in 1.52) made possible editing the configuration of the project. Still getting JS errors in the browser console : hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (hudson-behavior.js:424) at Array.forEach () at behavior.js:111 at Array.forEach () at behavior.js:107 at Array.forEach () at Object.applySubtree (behavior.js:93) at select.js:269 registerValidator @ hudson-behavior.js:424 (anonymous) @ behavior.js:111 (anonymous) @ behavior.js:107 applySubtree @ behavior.js:93 (anonymous) @ select.js:269 setTimeout (async) (anonymous) @ select.js:263 configure:1 [DOM] Found 2 elements with non-unique id #svn.remote.loc: (More info: https://goo.gl/9p2vKq) input#svn.remote.loc.setting-input.validated input#svn.remote.loc.setting-input.validated hudson-behavior.js:1311 Unable to find nearby server (anonymous) @ hudson-behavior.js:1311 (anonymous) @ prototype.js:853 each @ prototype.js:852 refillOnChange @ hudson-behavior.js:1308 (anonymous) @ select.js:77 (anonymous) @ behavior.js:111 (anonymous) @ behavior.js:107 applySubtree @ behavior.js:93 apply @ behavior.js:76 (anonymous) @ behavior.js:71 window.onload @ behavior.js:125 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Rui Chen commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 "uninstalling Violations plugin" works for us (maven project loading issue is gone), we are using v2.113 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Kimmo Toro commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Had a similar problem, was fixed after uninstalling Violations 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title io39d commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 View Image: image-2018-03-19-07-58-52-706.png updateListBox gets called before a following tr with the class="validation-error-area" exists / is being appended. That js error exists for long time in jenkins. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title io39d updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: io39d Attachment: image-2018-03-19-07-58-52-706.png 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Dennis Bliefernicht commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 That's true, however I can observe that while the _javascript_ TypeError in findFollowingTR still occurs (as others noted here that probably happened before already), the inability to edit maven projects did in fact disappear for us when upgrading to 2.111 (only other updates were the Durable Tasks 1.18 to 1.21 and Metrics 3.1.2.10 to 3.1.2.11); maybe the issue is now shadowed or handled better by existing code? 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Daniel Beck commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Dennis Bliefernicht JENKINS-49968 was introduced in 2.110, and this issue predates that. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Dennis Bliefernicht commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Actually upgrading to 2.111 fixed the issue completely for me. Could this be related to the fix to JENKINS-49968? Comments there mention breaking the validation logic which seems to be involved in this one 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ellinor Crux edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have had this same issue in Jenkins version 2.109 , violations version 0.7.11 with Freestyle jobs. I've looked at the thread dump for projects that I couldn't load and saw this: !image-2018-03-08-15-26-46-035.png|width=1222,height=149!It appears to be stuck loading something with the violations plugin. This appears to affect all the freestyle jobs that use the violations plugin on my server. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ellinor Crux commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have had this same issue in Jenkins version 2.109 with Freestyle jobs. I've looked at the thread dump for projects that I couldn't load and saw this: It appears to be stuck loading something with the violations plugin. This appears to affect all the freestyle jobs that use the violations plugin on my server. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ellinor Crux updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Ellinor Crux Attachment: image-2018-03-08-15-26-46-035.png 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 In my case the problem was only happening in Maven projects. We had both the Violations and Warnings plugins installed. Note that even after downgrading to 2.104 we are still getting the _javascript_ error from hudson-behavior.js. That error appears on most of our job's configuration pages. So I doubt it is related to whatever the problem was when we were running 2.107. It would be useful to fix that _javascript_ error just so it doesn't keep muddying the waters. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 In my case the problem was only happening in Maven projects. We had both the Violations and Warnings plugins installed.Note that even after downgrading to 2.104 we are still getting the _javascript_ error from hudson-behavior.js , although the pages are now working properly . That error appears on most of our job's configuration pages. So I doubt it is related to whatever the problem was when we were running 2.107. It would be useful to fix that _javascript_ error just so it doesn't keep muddying the waters. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Dennis Bliefernicht commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 At least in our installation it seems to be localized to Maven and Ivy projects only, although I couldn't reproduce it on a fresh instance yet (even with Violations / Warnings installed). One other thing I noticed is that the DOM tree seems to look okay after the problematic JS call failed (i.e. there is a proper following TR element then). Maybe the call somehow gets issued too early or there is some kind of race condition going on? 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Daniel Beck commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 From previous comments, it seems to happen in Maven projects, with Violations and Warnings plugins installed. Is that the consensus here? 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Dennis Bliefernicht commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 As an additional data point: in our current system (didn't manage to isolate the exact plugin combination yet) we can only observe this behaviour with Maven/Ivy Projects. Specifically it is enough to try to create a new job of these types as the renderer will fail on first enter of the UI already. This behaviour does not occur with Freestyle, Pipeline or External Jobs. However we also do have the Validations and Warnings plugins installed (which I cannot remove easily right now). Without knowing too much about the code around this: the target element ID of the failing element is select.setting-input.validated.select.credentials-select The surrounding DOM looks like this, so given from the select element in the last TR element there actually is no following TR to find here. The block seems to step from the Git configuration block and looking at a Freestyle project, those actually do have following TR elements. Repository URL Loading... Credentials Add Jenkins Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Jesse Glick commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 As a general note, I would kindly request that whenever coming across a reproducible case of Jenkins emitting an Uncaught TypeError: Cannot read property 'firstChild' of undefined for any reason, that in addition to fixing the root cause, the assignee also improve hudson-behavior.js to console.log a meaningful warning explaining what exactly it was looking for and where it failed to find that if possible, carry on other _javascript_ processing on the page, so that the UI is not completely broken 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have tried to reproduce the issue by installing Violations / Warnings and other plugins on 2.108, was unable to do so. From the screenshots I see that it something related to credentials: "select.credentials-select". It comes from Credentials plugin: https://github.com/jenkinsci/credentials-plugin/search?utf8=%E2%9C%93=%22credentials-select%22= Now the challenge is to find an overlap between Credentials and Violations 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev I upgraded Jenkins to 2.107 yesterday and upgraded all the plugins to their latest version. After that some of our jobs can no longer be configured. The page just shows "Loading" with a blinking icon. In addition, the chrome developer tool shows hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (hudson-behavior.js:424) at Array.forEach () at behavior.js:111 at Array.forEach () at behavior.js:107 at Array.forEach () at Object.applySubtree (behavior.js:93) at select.js:269registerValidator @ hudson-behavior.js:424(anonymous) @ behavior.js:111(anonymous) @ behavior.js:107applySubtree @ behavior.js:93(anonymous) @ select.js:269setTimeout (async)(anonymous) @ select.js:263 I am also seeing errors in the logs which may or may not be related. Caught exception evaluating: preloader.stateJson in /jenkins/blue/organizations/jenkins/js-modules/dashboard-ui/detail/PR-1/19/. Reason: java.lang.reflect.InvocationTargetException java.lang.NullPointerException at io.jenkins.blueocean.preload.PipelineActivityStatePreloader.getFetchData(PipelineActivityStatePreloader.java:67) at io.jenkins.blueocean.commons.RESTFetchPreloader.getStateJson(RESTFetchPreloader.java:64) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1738.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) 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.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) 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.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.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Moved BlueOcean error to JENKINS-49694 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Assignee: mike cirioli Oleg Nenashev 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 The last change in core's registerValidator _javascript_ was 5 years ago. the failing line is here: https://github.com/jenkinsci/jenkins/blame/5c8cc45900bf8d78058cecd471840bdbc88215d3/war/src/main/webapp/scripts/hudson-behavior.js#L424Apparently, "validation-error-area" is missing, and it causes the code to fail.Since Violations plugin has not been updated for long as well, my theory is that the plugin is a collateral damage as well. Likely recent update in something (e.g. analytics core) contributed an extension point implementation with a bogus field. Will see if I can reproduce that 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 The last change in core's registerValidator _javascript_ was 5 years ago. the failing line is here: https://github.com/jenkinsci/jenkins/blame/5c8cc45900bf8d78058cecd471840bdbc88215d3/war/src/main/webapp/scripts/hudson-behavior.js#L424 Apparently, "validation-error-area" is missing, and it causes the code to fail. Since Violations plugin has not been updated for long as well, my theory is that the plugin is a collateral damage as well. Likely recent update in something (e.g. analytics core) contributed an extension point with bogus field. Will see if I can reproduce that 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Thanks a lot for the analysis! There is a branch for Violations plugin with a serious rewrite by Tomas Bjerre: https://github.com/jenkinsci/violations-plugin/commits/master . If somebody can try that and verify that the issue dissapears, it could be an additional justification to move forward with that 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Component/s: warnings-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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Tomas Bjerre commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 For the record, future of violations plugin is discussed here: https://github.com/jenkinsci/violations-plugin/issues/88 I don't mind releasing it. Should require minimal effort from my part to maintain as I already maintain the lib for a bunch of other tools. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 We have violations 0.7.11 and warnings 4.6.5 installed. Since we are now back on 2.104 I can't say if they are the real cause of the problem. I also don't think it has anything to do with blue ocean, despite seeing the exception in the log. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Christoph Dreis commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Mauro Ferratello You're the man! That worked for me as well. I actually installed the violations plugin on the Docker instance and it works, but somehow it doesn't on our live setup. Fun fact: The plugin wasn't even used in the respective Maven Jobs, but in a different non-maven job 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Component/s: violation-columns-plugin Component/s: warnings-plugin Component/s: blueocean-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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Component/s: violations-plugin Component/s: violation-columns-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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Mauro Ferratello commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I've just solved it disabling 2 very outdated plugins: Violations (violations-plugin) Warnings But looking at the jenkins thread dumps I'm pretty sure was caused by Violations plugin Notes: Jenkins Version: 2.108 All plugins updated to the latest versions. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Christoph Dreis commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 And in some maven jobs I can't actually get to the point of seeing the spinner above the config page, but simply nothing happens and the request eventually times out. So I'd even argue it is JS related. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Christoph Dreis commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 It's actually unrelated to BlueOcean at all, I think. In our setup we don't have BlueOcean installed and it still fails. So I agree that there is something fishy in the core (or the maven-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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 IIUC the issue does not apprear on 2.104 with the latest BlueOcean release, am I right? If yes, something is clearly wrong in the core. How to diagnose the issue? Start Web Developer tools in your browser Open script console Open the Jenkins page which fails to load Debug _javascript_ to see which form fails and what is the reason for the first reported issue (what field/data cause that). You mileage may vary. I am not a JS developer, and I am definitely not the best source of such guidelines . Maybe Keith Zantow can provide more details 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Component/s: core 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Christoph Dreis commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Any ideas mike cirioli and Oleg Nenashev how to help finding the root cause of this? 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title mike cirioli commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I was also unable to reproduce this with the information provided. Nothing in the stack trace indicates to me that this is related to the XML change. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Christoph Dreis commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 As noted in JENKINS-49625 I appreciate the workaround, Ralph Goers. Yet, this doesn't seem to confirm that the root cause is actually in the XML file parsing. It only confirms that one could go back to 2.104. Yesterday, I set up a Jenkins Docker instance and couldn't reproduce the bug so far. Although a newly created config.xml looks the same on both our real Jenkins instance and the Docker one. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I didn't perform the work myself, but I am told that after downgrading to 2.104 the only change was to change the XML version in the files. to 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title mike cirioli commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 @reporter - if possible, can you attach the broken config.xml, as well as provide any relevant detail about the manual manipulations you had to perfrom for the the downgrade (ie. was it more than just changing the xml version in the config files?) 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev assigned an issue to mike cirioli Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Assignee: mike cirioli 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Assigned to mike cirioli then, It may be an issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Assigned to [~mikecirioli] then,It may be an issue impacting the LTS baseline selection 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 After research we determined that the problem is related to the jobs configuration files (config.xml) In the changelog we found information that in version 2.105 changes were made with updating xml version from 1.0 to 1.1. - https://jenkins.io/changelog/#v2.105 After rollback to version 2.104 and several manual manipulations Jenkins started with no error. So, what we have done: We downgraded Jenkins from 2.107 to 2.104 2.104 version is the latest stable version with support xml 1.0 In all xml-files we changed xml-version from 1.1 to 1.0 () After all changes Jenkins master started with no errors and look all jobs works fine 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title James Dumay commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Vivek Pandey not sure why our Blue Ocean preloader is running in this case - this appears to be rendering a classic jelly page. Something strange going on? 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail.See [^image-2018-02-19-12-03-57-775.png]I am also noticing that the number of div.credentials-select-control items seems to vary each time I run it. It will contain anywhere from 4 to 6 items. I have no idea why that would change. I should also add that we see the same _javascript_ error on other pages but only ones with the credentials selection seem to fail to completely load. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail.See https://issues.jenkins-ci.org/secure/attachment/41529/ [^ image-2018-02-19-12-03-57-775.png ]I am also noticing that the number of div.credentials-select-control items seems to vary each time I run it. It will contain anywhere from 4 to 6 items. I have no idea why that would change. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail. ! See https://issues.jenkins-ci.org/secure/attachment/41529/ image-2018-02-19-12- 06 03 - 02 57 - 174 775 .png ! 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail. !image-2018-02-19-12- 03 06 - 57 02 - 775 174 .png! 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Digging further we see that select.js updateListBox is calling hudson-behavior.js findFollowingTR which is returning undefined, causing the subsequent code to fail. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Ralph Goers Attachment: image-2018-02-19-12-03-57-775.png 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 We were on 2.76. I am not sure to tell you the versions of all the plugins we were using. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Which version have been using before the upgrade BTW? 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Labels: regression 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 In stepping through the code where the error is occurring I can see it is going through an HTMLCollection that contains a set of div.credentials-select-control objects. I am having some trouble getting any deeper. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I created a new Job and selected "Maven Project" as the type. It has the same problem without me configuring anything. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have no idea if this will help but here is a screen shot of what I am seeing in the debugger when stopped Looking further at the line that fails. exception we see !image Exception:TypeError: Cannot read property 'firstChild' of undefined at updateListBox (https://jenkins.nextiva.xyz/jenkins/adjuncts/7c62842d/lib/form/select/select.js:8:67) at https://jenkins.nextiva.xyz/jenkins/adjuncts/7c62842d/lib/form/select/select.js:79:13 at h (https://jenkins.nextiva.xyz/jenkins/static/7c62842d/scripts/hudson - 2018 behavior.js:1298:9) at refillOnChange (https://jenkins.nextiva.xyz/jenkins/static/7c62842d/scripts/hudson - 02 behavior.js:1313:5) at https://jenkins.nextiva.xyz/jenkins/adjuncts/7c62842d/lib/form/select/select.js:77:9 at Array.forEach () at https://jenkins.nextiva.xyz/jenkins/static/7c62842d/scripts/behavior.js:111:30 at Array.forEach () at https://jenkins.nextiva.xyz/jenkins/static/7c62842d/scripts/behavior.js:107:27 at Array.forEach ()arguments:Arguments(3) [select.setting - 19 input.select.credentials - 10 select, "/jenkins/view/Calendar/job/calendar - 06 dry - 25 run - 260 rev/descriptorByName/bitbucketpullrequestbuilder . png! bitbucketpullrequestbuilder.BitbucketBuildTrigger/fillCredentialsIdItems", F, callee: ƒ, Symbol(Symbol.iterator): ƒ] 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
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have no idea if this will help but here is a screen shot of what I am seeing in the debugger when stopped at the line that fails. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Ralph Goers Attachment: image-2018-02-19-10-06-25-260.png 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Adding links to 2 other issues which seem to be similar. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Yes - this is Jenkins downloaded from your site as a war on Friday. I am adding as much information as I can here in the hopes that something in the logs is related to what is happening in the UI. After upgrading the Maven plugin I now notice. I am not sure if this was there previously and I just missed it or if it is new to the restart. Feb 19, 2018 9:32:00 AM WARNING hudson.init.impl.InstallUncaughtExceptionHandler lambda$init$0 null org.apache.commons.jelly.JellyTagException: jar:file:/opt/jenkins/apache-tomcat-7.0.65/webapps/jenkins/WEB-INF/lib/jenkins-core-2.107.jar!/hudson/model/View/index.jelly:42:43: org.apache.commons.jelly.JellyTagException: jar:file:/opt/jenkins/apache-tomcat-7.0.65/webapps/jenkins/WEB-INF/lib/jenkins-core-2.107.jar!/lib/hudson/projectViewRow.jelly:38:17: java.net.SocketException: Broken pipe 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.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 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.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:140) at org.kohsuke.stapler.IndexViewDispatcher.dispatch(IndexViewDispatcher.java:30) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Keith Zantow commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Just to be clear, you're looking at classic Jenkins, correct? hudson-behavior.js has nothing to do with Blue Ocean. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Upgrading the Maven plugin seems to have resolved the second stack trace but I still cannot view the configuration for several jobs. They are still getting the _javascript_ error I noted above. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 yes (for the second reported issue) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 The Maven Integration Plugin? That is currently at 3.0. I see 3.1 just became available. Is that what I need to upgrade? 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Blue Ocean was upgraded to 1.4.2 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 The second issue is JENKINS-45892, which is fixed in the latest Maven Plugin release 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I am also seeing the trace below. The strange thing is that I am not trying to edit that configuration, although it is possible someone else might be. - JENKINS-45892 - : reference to hudson.maven.MavenModuleSet@6b5ca68a[NotificationService_DryRun] being saved from unexpected /opt/jenkins/.jenkins/jobs/NotificationService_DryRun/builds/477/build.xml java.lang.IllegalStateException at hudson.XmlFile.replaceIfNotAtTopLevel(XmlFile.java:222) at hudson.model.AbstractItem.writeReplace(AbstractItem.java:492) at sun.reflect.GeneratedMethodAccessor165.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:89) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:141) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I am also seeing JENKINS-45892: reference to hudson.maven.MavenModuleSet@6b5ca68a[NotificationService_DryRun] being saved from unexpected /opt/jenkins/.jenkins/jobs/NotificationService_DryRun/builds/477/build.xml java.lang.IllegalStateException at hudson.XmlFile.replaceIfNotAtTopLevel(XmlFile.java:222) at hudson.model.AbstractItem.writeReplace(AbstractItem.java:492) at sun.reflect.GeneratedMethodAccessor165.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:89) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:141) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Please provide a version of BO you use 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Looks like a BlueOcean issue. NullPointerException is always a bug IMO. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Component/s: blueocean-plugin Component/s: core 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ralph Goers created an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-02-19 15:50 Environment: Centos 7 Java 8 Priority: Major Reporter: Ralph Goers I upgraded Jenkins to 2.107 yesterday and upgraded all the plugins to their latest version. After that some of our jobs can no longer be configured. The page just shows "Loading" with a blinking icon. In addition, the chrome developer tool shows hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (hudson-behavior.js:424) at Array.forEach () at behavior.js:111 at Array.forEach () at behavior.js:107 at Array.forEach () at Object.applySubtree (behavior.js:93) at select.js:269 registerValidator @ hudson-behavior.js:424 (anonymous) @ behavior.js:111 (anonymous) @ behavior.js:107 applySubtree @ behavior.js:93 (anonymous) @ select.js:269 setTimeout (async) (anonymous) @ select.js:263 I am also seeing errors in the logs which may or may not be related. Caught exception evaluating: preloader.stateJson in /jenkins/blue/organizations/jenkins/js-modules/dashboard-ui/detail/PR-1/19/. Reason: java.lang.reflect.InvocationTargetException java.lang.NullPointerException at io.jenkins.blueocean.preload.PipelineActivityStatePreloader.getFetchData(PipelineActivityStatePreloader.java:67) at io.jenkins.blueocean.commons.RESTFetchPreloader.getStateJson(RESTFetchPreloader.java:64) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1738.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at
