[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Hi Wadeck Follonier - 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! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Hi Wadeck Follonier, 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Thanks Wadeck Follonier, I will try a deployment with the WAR once it becomes available and let you know my results. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam edited a comment on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Answers:1) I did not try this on Windows 10. Jenkins 2.138 worked correctly. Only after upgrade to 2.150.2+ did issues start. If I revert to 2.138, the workspace and artifacts will work again, and then going back to 2.150.2+ they stop working (currently on 2.164 but i usually prefer to track LTS).Note: All the jobs were build using pre 2.138 versions (I started on 2.73), so those built the directory trees, etc. that have been carried through the LTS upgrade cycles. Only on 2.150.2+ did the workspace/artifacts start having issue.2) Included3) I am using Windows Server 2016 Version 1607. Docker was installed through powershell, PSGallery, so it is MSFT Docker.{{Install-Module -Name DockerMsftProvider -Repository PSGallery}}Docker runner:{{$JENKINS_IP = ""}} {{$JENKINS_VERSION = "2.164"}} {{$HOST_JENKINS_HOME = "d:/data/jenkins"}} {{$JENKINS_HOME = "c:/jenkins"}} {{$HOST_BUILD_ARCHIVE = "d:/data/buildarchive"}} {{$JENKINS_BUILD_ARCHIVE = "c:/buildarchive"}}{{docker run -d --ip ${JENKINS_IP} `}}{{--mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} `}}{{--mount type=bind,source=${HOST_BUILD_ARCHIVE},target=${JENKINS_BUILD_ARCHIVE} `}} {{"/jenkins-on-windowsservercore:$JENKINS_VERSION"}} C: is the Jenkins point within the container, which mounts from D: outside the container as the docker mount/data drive.For the web UI, the Jenkins port is exposed via the Dockerfile (EXPOSE 8080). When I build the container, Dockefile uses a powershell command to create an empty C:/jenkins within the container for the mount points.{ \ {RUN }} \ {{ New-Item -ItemType Directory -Force -Path $env:JENKINS_HOME; }} \ {{ New-Item -ItemType Directory -Force -Path $env:JENKINS_BUILD_ARCHIVE;}} Staring Jenkins (via powershell startup script):{{& java.exe -jar c:/jenkins.war --sessionTimeout=720 --sessionEviction=720}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam edited a comment on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Answers:1) I did not try this on Windows 10. Jenkins 2.138 worked correctly. Only after upgrade to 2.150.2+ did issues start. If I revert to 2.138, the workspace and artifacts will work again, and then going back to 2.150.2+ they stop working (currently on 2.164 but i usually prefer to track LTS).Note: All the jobs were build using pre 2.138 versions (I started on 2.73), so those built the directory trees, etc. that have been carried through the LTS upgrade cycles. Only on 2.150.2+ did the workspace/artifacts start having issue.2) Included3) I am using Windows Server 2016 Version 1607. Docker was installed through powershell, PSGallery, so it is MSFT Docker.{{Install-Module -Name DockerMsftProvider -Repository PSGallery}}Docker runner:{{$JENKINS_IP = ""}} {{$JENKINS_VERSION = "2.164"}} {{$HOST_JENKINS_HOME = "d:/data/jenkins"}} {{$JENKINS_HOME = "c:/jenkins"}} {{$HOST_BUILD_ARCHIVE = "d:/data/buildarchive"}} {{$JENKINS_BUILD_ARCHIVE = "c:/buildarchive"}}{{ docker run -d --ip ${JENKINS_IP} `}} {{ {{ --mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} `}} }} {{ {{ --mount type=bind,source=${HOST_BUILD_ARCHIVE},target=${JENKINS_BUILD_ARCHIVE} `}} }} {{"/jenkins-on-windowsservercore:$JENKINS_VERSION"}} C: is the Jenkins point within the container, which mounts from D: outside the container as the docker mount/data drive.For the web UI, the Jenkins port is exposed via the Dockerfile (EXPOSE 8080). When I build the container, Dockefile uses a powershell command to create an empty C:/jenkins within the container for the mount points.{\{RUN }} \{{ New-Item -ItemType Directory -Force -Path $env:JENKINS_HOME; }} \{{ New-Item -ItemType Directory -Force -Path $env:JENKINS_BUILD_ARCHIVE;}} Staring Jenkins (via powershell startup script):{{& java.exe -jar c:/jenkins.war --sessionTimeout=720 --sessionEviction=720}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam edited a comment on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Answers:1) I did not try this on Windows 10. Jenkins 2.138 worked correctly. Only after upgrade to 2.150.2+ did issues start. If I revert to 2.138, the workspace and artifacts will work again, and then going back to 2.150.2+ they stop working (currently on 2.164 but i usually prefer to track LTS).Note: All the jobs were build using pre 2.138 versions (I started on 2.73), so those built the directory trees, etc. that have been carried through the LTS upgrade cycles. Only on 2.150.2+ did the workspace/artifacts start having issue.2) Included3) I am using Windows Server 2016 Version 1607. Docker was installed through powershell, PSGallery, so it is MSFT Docker.{{Install-Module -Name DockerMsftProvider -Repository PSGallery}}Docker runner:{{$JENKINS_IP = ""}}{{$JENKINS_VERSION = "2.164"}}{{$HOST_JENKINS_HOME = "d:/data/jenkins"}}{{$JENKINS_HOME = "c:/jenkins"}}{{$HOST_BUILD_ARCHIVE = "d:/data/buildarchive"}}{{$JENKINS_BUILD_ARCHIVE = "c:/buildarchive"}}{{ {{ docker run -d --ip ${JENKINS_IP} `}} }} {{ --mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} `}}{{ --mount type=bind,source=${HOST_BUILD_ARCHIVE},target=${JENKINS_BUILD_ARCHIVE} `}}{{ "/jenkins-on-windowsservercore:$JENKINS_VERSION"}} C: is the Jenkins point within the container, which mounts from D: outside the container as the docker mount/data drive.For the web UI, the Jenkins port is exposed via the Dockerfile (EXPOSE 8080). When I build the container, Dockefile uses a powershell command to create an empty C:/jenkins within the container for the mount points.{ \ {RUN \ }} \ {{ New-Item -ItemType Directory -Force -Path $env:JENKINS_HOME; \ }} \ {{ New-Item -ItemType Directory -Force -Path $env:JENKINS_BUILD_ARCHIVE;}} Staring Jenkins (via powershell startup script):{{& java.exe -jar c:/jenkins.war --sessionTimeout=720 --sessionEviction=720}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam edited a comment on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Answers:1) I did not try this on Windows 10. Jenkins 2.138 worked correctly. Only after upgrade to 2.150.2+ did issues start. If I revert to 2.138, the workspace and artifacts will work again, and then going back to 2.150.2+ they stop working (currently on 2.164 but i usually prefer to track LTS).Note: All the jobs were build using pre 2.138 versions (I started on 2.73), so those built the directory trees, etc. that have been carried through the LTS upgrade cycles. Only on 2.150.2+ did the workspace/artifacts start having issue.2) Included3) I am using Windows Server 2016 Version 1607. Docker was installed through powershell, PSGallery, so it is MSFT Docker.{{Install-Module -Name DockerMsftProvider -Repository PSGallery}}Docker runner:{{$JENKINS_IP = ""}} {{$JENKINS_VERSION = "2.164"}} {{$HOST_JENKINS_HOME = "d:/data/jenkins"}} {{$JENKINS_HOME = "c:/jenkins"}} {{$HOST_BUILD_ARCHIVE = "d:/data/buildarchive"}} {{$JENKINS_BUILD_ARCHIVE = "c:/buildarchive"}} {{ docker run -d --ip ${JENKINS_IP} ` }} {{ {{ --mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} `}} }} {{ {{ --mount type=bind,source=${HOST_BUILD_ARCHIVE},target=${JENKINS_BUILD_ARCHIVE} `}} }} {{ "/jenkins-on-windowsservercore:$JENKINS_VERSION"}} C: is the Jenkins point within the container, which mounts from D: outside the container as the docker mount/data drive.For the web UI, the Jenkins port is exposed via the Dockerfile (EXPOSE 8080). When I build the container, Dockefile uses a powershell command to create an empty C:/jenkins within the container for the mount points.{\{RUN }} \{{ New-Item -ItemType Directory -Force -Path $env:JENKINS_HOME; }} \{{ New-Item -ItemType Directory -Force -Path $env:JENKINS_BUILD_ARCHIVE;}} Staring Jenkins (via powershell startup script):{{& java.exe -jar c:/jenkins.war --sessionTimeout=720 --sessionEviction=720}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam commented on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Answers: 1) I did not try this on Windows 10. Jenkins 2.138 worked correctly. Only after upgrade to 2.150.2+ did issues start. If I revert to 2.138, the workspace and artifacts will work again, and then going back to 2.150.2+ they stop working (currently on 2.164 but i usually prefer to track LTS). Note: All the jobs were build using pre 2.138 versions (I started on 2.73), so those built the directory trees, etc. that have been carried through the LTS upgrade cycles. Only on 2.150.2+ did the workspace/artifacts start having issue. 2) Included 3) I am using Windows Server 2016 Version 1607. Docker was installed through powershell, PSGallery, so it is MSFT Docker. Install-Module -Name DockerMsftProvider -Repository PSGallery Docker runner: $JENKINS_IP = "" $JENKINS_VERSION = "2.164" $HOST_JENKINS_HOME = "d:/data/jenkins" $JENKINS_HOME = "c:/jenkins" $HOST_BUILD_ARCHIVE = "d:/data/buildarchive" $JENKINS_BUILD_ARCHIVE = "c:/buildarchive" docker run -d --ip ${JENKINS_IP} ` {{ --mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} `}} {{ --mount type=bind,source=${HOST_BUILD_ARCHIVE},target=${JENKINS_BUILD_ARCHIVE} `}} {{ "/jenkins-on-windowsservercore:$JENKINS_VERSION"}} C: is the Jenkins point within the container, which mounts from D: outside the container as the docker mount/data drive. For the web UI, the Jenkins port is exposed via the Dockerfile (EXPOSE 8080). When I build the container, Dockefile uses a powershell command to create an empty C:/jenkins within the container for the mount points. {{RUN }} {{ New-Item -ItemType Directory -Force -Path $env:JENKINS_HOME; }} {{ New-Item -ItemType Directory -Force -Path $env:JENKINS_BUILD_ARCHIVE;}} Staring Jenkins (via powershell startup script): & java.exe -jar c:/jenkins.war --sessionTimeout=720 --sessionEviction=720
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Hi Wadeck Follonier, here is the output from the script console. Used the same job as all the items captured above for consistency. [true, C:] [true, c:\jenkins] [true, c:\jenkins\workspace, false] [true, c:\jenkins\workspace\Au, false, false] [true, c:\jenkins\workspace\Au, false, false] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam edited a comment on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Hi [~wfollonier], here is the output from the script console. Used the same job as all the items captured above for consistency. Note: I'm still using the -D directive above, I'll have to restart the instance without that directive if that information is also required. [true, C: \ ][true, c:\jenkins][true, c:\jenkins\workspace, false][true, c:\jenkins\workspace\Au, false, false][true, c:\jenkins\workspace\Au, false, false] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam edited a comment on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Hi [~wfollonier], here is the output from the script console. Used the same job as all the items captured above for consistency.Note: I'm still using the -D directive above, I'll have to restart the instance without that directive if that information is also required.[true, C:] [true, c:\jenkins] [true, c:\jenkins\workspace, false] [true, c:\jenkins\workspace\Au, false, false] [true, c:\jenkins\workspace\Au, false, false] For stack traces, I dont' see anything on the console when I attempt to access the project (for it's artifacts), and when I access the workspace the console displays:Feb 15, 2019 12:03:25 PM hudson.model.DirectoryBrowserSupport serveFileWARNING: Trying to access a file outside of the directory, target:Let me know which console and/or debug you're after for more detail. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam edited a comment on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Hi [~wfollonier], here is the output from the script console. Used the same job as all the items captured above for consistency. I'm currently using version 2.164. Note: I'm still using the -D directive above, I'll have to restart the instance without that directive if that information is also required.[true, C:] [true, c:\jenkins] [true, c:\jenkins\workspace, false] [true, c:\jenkins\workspace\Au, false, false] [true, c:\jenkins\workspace\Au, false, false]For stack traces, I dont' see anything on the console when I attempt to access the project (for it's artifacts), and when I access the workspace the console displays:Feb 15, 2019 12:03:25 PM hudson.model.DirectoryBrowserSupport serveFileWARNING: Trying to access a file outside of the directory, target:Let me know which console and/or debug you're after for more detail. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) For thoroughness, I restarted the instance removing the -Dhudson.model.DirectoryBrowserSupport.allowSymlinkEscape=true directive from the startup, and ran the script code above: [true, C:] [true, c:\jenkins] [true, c:\jenkins\workspace, false] [true, c:\jenkins\workspace\Au, false, false] [true, c:\jenkins\workspace\Au, false, false] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Daniel Beck Correct, both the HTTP 403 and the console end with no information after "target:". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Daniel Beck Thanks for the information. I tried adding that to the startup, no change (artifacts and workspace still unavailable). Startup command via powershell script: & java.exe -Dhudson.model.DirectoryBrowserSupport.allowSymlinkEscape=true -jar c:/jenkins.war --sessionTimeout=720 --sessionEviction=720 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam edited a comment on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) [~danielbeck] [~wfollonier] Is there any additional information required? We are impacted in one of our deployed instances with this configuration currently. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Daniel Beck Wadeck Follonier Is there any additional information required? We are impacted in one of our deployed instances with this configuration currently. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam edited a comment on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Job directory structure was created by Jenkins itself from initial deployment version of 2.73.2. Upgrades through multiple LTS versions to 2.138 worked as expected.Jenkins uses a Docker bind mount into the container to map c:\jenkins to the external bind mount point on the host file system, and all Jenkins files reside within in the Jenkins created directory tree. When starting the container, docker variables and mount point:$HOST_JENKINS_HOME = "d:/data/jenkins"$JENKINS_HOME = "c:/jenkins"--mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} Directory Jenkins directory listing (from within the container) included in attachment : jenkins_dir_tree_20190213_1 . txt
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam edited a comment on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Job directory structure was created by Jenkins itself from initial deployment version of 2.73.2. Upgrades through multiple LTS versions to 2.138 worked as expected.Jenkins uses a Docker bind mount into the container to map c:\jenkins to the external bind mount point on the host file system, and all Jenkins files reside within in the Jenkins created directory tree. When starting the container, docker variables and mount point:$HOST_JENKINS_HOME = "d:/data/jenkins" $JENKINS_HOME = "c:/jenkins"--mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME}Jenkins directory listing (from within the container) included in attachment: jenkins_dir_tree_20190213_1.txt
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam commented on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Job directory structure was created by Jenkins itself from initial deployment version of 2.73.2. Upgrades through multiple LTS versions to 2.138 worked as expected. Jenkins uses a Docker bind mount into the container to map c:\jenkins to the external bind mount point on the host file system, and all Jenkins files reside within in the Jenkins created directory tree. When starting the container, docker variables and mount point: $HOST_JENKINS_HOME = "d:/data/jenkins" $JENKINS_HOME = "c:/jenkins" --mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} Directory listing included in attachment.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam Attachment: jenkins_dir_tree_20190213_1.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam Summary: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam 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.h2. HTTP ERROR 403Problem accessing /job//ws/. Reason:Trying to access a file outside of the directory, target: [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty] 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam 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.h2. HTTP ERROR 403Problem accessing /job//ws/. Reason:Trying to access a file outside of the directory, target: [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty] 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.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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam 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. h2. HTTP ERROR 403 " Problem accessing /job/< jobname job_name_redacted >/ws/. Reason:Trying to access a file outside of the directory, target: " [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty] 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.Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam 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."Problem accessing /job//ws/. Reason:Trying to access a file outside of the directory, target:"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.Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible as expected.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."Problem accessing /job//ws/. Reason:Trying to access a file outside of the directory, target:"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. Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+
Title: Message Title Jeremy Kam created an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-13 00:19 Environment: Windows Server 2016, MSFT Docker, OpenJDK 8 Container Priority: Major Reporter: Jeremy Kam Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible as expected. 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. "Problem accessing /job//ws/. Reason: Trying to access a file outside of the directory, target:" 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. Add Comment
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam Summary: Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
