Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56114

Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

    • Jenkins 2.168

      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.

          [JENKINS-56114] Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

          I will provide a WAR in a moment (still today I hope) so that you can test by yourself if my changes are effectice in your case or not

          Wadeck Follonier added a comment - I will provide a WAR in a moment (still today I hope) so that you can test by yourself if my changes are effectice in your case or not

          The WAR will be available in this PR once the build is completed.

          Wadeck Follonier added a comment - The WAR will be available in this PR once the build is completed.

          Jeremy Kam added a comment -

          Thanks wfollonier, I will try a deployment with the WAR once it becomes available and let you know my results.

          Jeremy Kam added a comment - Thanks wfollonier , I will try a deployment with the WAR once it becomes available and let you know my results.

          jkam As the build is currently failing, you can use this link in the meantime: https://drive.google.com/file/d/1cRd_DKpJF9hezf1q9mM2LDMHUM_vQGCp/view?usp=sharing

          I just build the war locally from the branch of the PR, feel free to don't trust and wait for the build to success

          Wadeck Follonier added a comment - jkam As the build is currently failing, you can use this link in the meantime: https://drive.google.com/file/d/1cRd_DKpJF9hezf1q9mM2LDMHUM_vQGCp/view?usp=sharing I just build the war locally from the branch of the PR, feel free to don't trust and wait for the build to success

          The WAR is now available from the build on https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-3914/3/artifacts, search for jenkins-war-2.167-rc28022.09203244c3f8.war.

          Wadeck Follonier added a comment - The WAR is now available from the build on https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-3914/3/artifacts , search for jenkins-war-2.167-rc28022.09203244c3f8.war .

          Jeremy Kam added a comment -

          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.

          Jeremy Kam added a comment - 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.

          jkam Thank you very much for the feedback!

          Wadeck Follonier added a comment - jkam Thank you very much for the feedback!

          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)

          Wadeck Follonier added a comment - jkam That's really appreciated to receive such feedback, thank you The correction will normally be part of the next weekly (~2.168)

          Oleg Nenashev added a comment -

          It has been fixed in 2.168, and most likely it caused JENKINS-56578

          Oleg Nenashev added a comment - It has been fixed in 2.168, and most likely it caused  JENKINS-56578

            wfollonier Wadeck Follonier
            jkam Jeremy Kam
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: