-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Jenkins ver. 2.19.3
BlueOcean beta 1.0.0-b12
Kernel release: 3.16.0-4-amd64
Kernel version: #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19)
OS: Debian GNU/Linux 8.6 (jessie)
(bitnami deployment)
-
-
tasman, frank
After using the blueocean plugin for a few days suddenly stops. I restart it and when I try to login I get either a stack trace or a resource not found tomcat error I believe (forgot to screenshot this).
I also get a jsessionid in the url all the time. Clearing cookies and trying t login again does not work. Using chromium as my default browser.
Then switched to firefox and tried loggin in: succes. I then deactivated all blueocean related plugins, the problem disappeared and I could then login again at chromium.
[JENKINS-40116] Crash on login when using blueocean plugin
Assignee | New: Tom FENNELLY [ tfennelly ] |
Epic Link | New: JENKINS-35749 [ 171790 ] |
Sprint | New: tasman [ 136 ] | |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Sprint | Original: tasman [ 136 ] | New: tasman, frank [ 136, 156 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |
We need an NPE check in ResourceCacheControl for when the request path is empty.