-
Bug
-
Resolution: Duplicate
-
Blocker
-
None
-
Jenkins 2.108
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
- duplicates
-
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
[JENKINS-49625] Config pages of Maven jobs do no load
Christoph Dreis
created issue -
Christoph Dreis
made changes -
| Environment | New: Jenkins 2.108 |
Christoph Dreis
made changes -
| Description |
Original:
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 |
New:
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 |
Christoph Dreis
made changes -
| Attachment | New: startup_log.txt [ 41526 ] |
Christoph Dreis
added a comment - oleg_nenashev Please find the log attached We're actually seeing a similar behavior as JENKINS-49630
Yet, this seems to be unrelated to Bitbucket, but to a normal git setup.
descriptorByName/hudson.plugins.git.UserRemoteConfig/fillCredentialsIdItems
{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}
Christoph Dreis
added a comment - - edited We're actually seeing a similar behavior as JENKINS-49630
Yet, this seems to be unrelated to Bitbucket, but to a normal git setup.
descriptorByName/hudson.plugins.git.UserRemoteConfig/fillCredentialsIdItems
{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} | Link |
New:
This issue duplicates |
Christoph Dreis
added a comment - 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.
Christoph Dreis
added a comment - 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.
It is not possible to say anything without startup logs