Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
Windows Server 2016, MSFT Docker, OpenJDK 8 Container
-
-
Jenkins 2.168
Description
Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected. Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.
After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
HTTP ERROR 403
Problem accessing /job/<job_name_redacted>/ws/. Reason:
Trying to access a file outside of the directory, target:
Powered by Jetty:// 9.4.z-SNAPSHOT
Attempted upgrade of container to OpenJDK 11, same errors occur.
Job artifacts are created and present on local file system. Workspace is created and present on local file system. Job will build project, just won't present the results/workspace through the UI.
Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
IIS reverse proxy reference: https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS (instead of localhost and host file, used container IP address directly). Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.
Attachments
Issue Links
- causes
-
-
- Open
-
- links to
Activity
Jeremy Kam
added a comment - Hi wfollonier - we ran though various jobs, screens, etc. as well and everything seems to working as expected. Thanks for your work on this and the turnaround on a fix!
Jeremy Kam
added a comment - Hi wfollonier - we ran though various jobs, screens, etc. as well and everything seems to working as expected. Thanks for your work on this and the turnaround on a fix! jkam That's really appreciated to receive such feedback, thank you 
The correction will normally be part of the next weekly (~2.168)
Hi wfollonier, I have retrieved the CI build and deployed to my environment. I can report that the fix is successful. We are able to see the workspace and artifacts now. We have also run several jobs and so far have not encountered other issues.