-
Bug
-
Resolution: Unresolved
-
Critical
-
None
Jenkins v2.101
Latest for all BlueOcean plugins (1.3.5)
When opening a job url for Blue Ocean, for example from Bitbucket pull request build status if the user isn't logged into Jenkins it shows:
HTTP ERROR 404
Problem accessing /job/power-designer/job/PR-157/3/display/redirect. Reason:
Not Found
When the user goes to the jenkins server and logs in the job url then works correctly. Blue Ocean job url needs to redirect user to a login screen instead of this 404 error.
[JENKINS-48903] Blue Ocean job gets 404 when user isn't logged in
Description |
Original:
When opening a job url for Blue Ocean, for example from Bitbucket pull request build status if the user isn't logged into Jenkins it shows: h2. HTTP ERROR 404 Problem accessing /job/power-designer/job/PR-157/3/display/redirect. Reason: Not Found When the user goes to the jenkins server and logs in the job url then works correctly. Blue Ocean job url needs to redirect user to a login screen instead of this 404 error. |
New:
Jenkins v2.101 Latest for all BlueOcean plugins (1.3.5) When opening a job url for Blue Ocean, for example from Bitbucket pull request build status if the user isn't logged into Jenkins it shows: h2. HTTP ERROR 404 Problem accessing /job/power-designer/job/PR-157/3/display/redirect. Reason: Not Found When the user goes to the jenkins server and logs in the job url then works correctly. Blue Ocean job url needs to redirect user to a login screen instead of this 404 error. |
Attachment | New: image-2018-01-15-23-20-48-813.png [ 41128 ] |