[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis commented on JENKINS-49625 Re: Config pages of Maven jobs do no load Indeed related, but can be closed as the root cause provided in JENKINS-49630 is in fact the 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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis closed an issue as Duplicate Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Change By: Christoph Dreis Status: Open Closed Resolution: Duplicate 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 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 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 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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis commented on JENKINS-49625 Re: Config pages of Maven jobs do no load 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. 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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis commented on JENKINS-49625 Re: Config pages of Maven jobs do no load The behaviour is very inconsistent. On some jobs I'm not even getting to the config page at all. On some I see the spinner as described above and in JENKINS-49630. The one where I can't see the page at all is actually a new Maven Job I tried to create in order to test things. 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-49625) Config pages of Maven jobs do no load
Title: Message Title
Christoph Dreis edited a comment on JENKINS-49625
Re: Config pages of Maven jobs do no load
We're actually seeing a similar behavior as JENKINS-49630 Yet, this seems to be unrelated to Bitbucket, but to a normal git setup.{color:#22}descriptorByName/hudson.plugins.git.UserRemoteConfig/fillCredentialsIdItems{color}\{code}updateListBox (select.js:4)(anonymous) (select.js:79)h (hudson-behavior.js:1304)refillOnChange (hudson-behavior.js:1319)(anonymous) (select.js:77)(anonymous) (behavior.js:111)(anonymous) (behavior.js:107)applySubtree (behavior.js:93)(anonymous) (select.js:269)setTimeout (async)(anonymous) (select.js:263)\{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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis commented on JENKINS-49625 Re: Config pages of Maven jobs do no load We're actually seeing a similar behavior as JENKINS-49630 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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis updated an issue Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Change By: Christoph Dreis Attachment: startup_log.txt 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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis commented on JENKINS-49625 Re: Config pages of Maven jobs do no load Oleg Nenashev Please find the log attached 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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis updated an issue Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Change By: Christoph Dreis Hi,we did an upgrade from 2.103 to 2.108 today. After the update we noticed that some xUnit related jobs were failing.So we went ahead and tried to open the job configurations page and failed. We were and are unable to open job configuration pages. This seems to "only" affect Maven jobs for us, but we see no error logs or anything else that would give us a hint what the root cause of this error is.I already tried creating a fresh job, but this doesn't work as well. Any help is highly appreciated as this is basically blocking any work with Jenkins at the moment. It would also help if you could clarify if the xUnit step problem might be related or not. Cheers,Christoph 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
[JIRA] (JENKINS-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis updated an issue Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Change By: Christoph Dreis Environment: Jenkins 2.108 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-49625) Config pages of Maven jobs do no load
Title: Message Title Christoph Dreis created an issue Jenkins / JENKINS-49625 Config pages of Maven jobs do no load Issue Type: Bug Assignee: Unassigned Components: core, maven-plugin Created: 2018-02-19 13:29 Priority: Blocker Reporter: Christoph Dreis Hi, we did an upgrade from 2.103 to 2.108 today. After the update we noticed that some xUnit related jobs were failing. So we went ahead and tried to open the job configurations page and failed. We were and are unable to open job configuration pages. This seems to "only" affect Maven jobs for us, but we see no error logs or anything else that would give us a hint what the root cause of this error is. I already tried creating a fresh job, but this doesn't work as well. Any help is highly appreciated as this is basically blocking any work with Jenkins at the moment. Cheers, Christoph Add Comment
