[JIRA] (JENKINS-54346) tee keeps file open
Title: Message Title Glenn Herbert commented on JENKINS-54346 Re: tee keeps file open Just running into this today. For I workaround i switched to use powershell as follows: bat ''' powershell "cmd /c '.\your.bat' | tee output.txt" ''' Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195001.1540906753000.392.1582757881273%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Same here, been running with SymlinkEscape=true for quite a while. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197816.1550852223000.3402.1569249360313%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Our use of (Windows) symlinks (directory junctions) is purely for directories. We store build artifacts on a corporate (remote) NAS drive (multi-TB), but use the jenkins userContent and its built-in file server as a way to 1) download artifacts via jenkins URL (ie curl http:/myJenkins/userContent/symlink/path/to/artifact), or 2) navigate to specific artifacts. We don't ever request a zip on the actual symlinked folder but some content that resides within that symlinked folder tree. I would not expect a zip file to contain a symlink but rather its resolved target. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197816.1550852223000.1930.1568990160451%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Thanks Matt Sicker for verification. 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-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 The problem continues to persist even after upgrading all plugins and to the latest Jenkins version 2.168. The workaround we are using is to pre-zip the fetched content, to bypass the non-functional Jenkins zip functionality, so this is not as high a priority as it was. However, it's still lost functionality that should be fixed. 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-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title
Glenn Herbert edited a comment on JENKINS-56249
Re: userContent *zip* (all files in zip) stopped working at 2.164
Wadeck Follonier: I cannot try using the WAR from JENKINS-56114 as this is a production system. I will try to bring up a new jenkins and try it.To answer your other questions: * we are using the escape hatch -Dhudson.model.DirectoryBrowserSupport.allowSymlinkEscape=true * we are NOT using docker, just running the jenkins windows service * userContent has a mix of files, folders, and directory junctions (symlinks)The build logs have no real information in them as it was a silent failure, because the zip was empty. The gradle code used was{quote} def f = new File("$buildOutput/staging.zip") if (!f.exists()) { new URL('http://myJenkins:8080/userContent/archive/components/Staging/* * zip* * /staging.zip').withInputStream\{ i -> f.withOutputStream{ it << i }} }copy Unknown macro: \ { from zipTree(f.getAbsolutePath()) into("$buildOutput/config/") }f.delete(){quote}From the UI, this is the Staging folder (this is not the actual folder used but shows the problem):!image-2019-02-28-16-52-19-863.png!If i then click on the (all files in zip), the Staging.zip file gets generated but its only 1KB!image-2019-02-28-16-53-48-739.png!And if its opened with 7zip the file is empty!image-2019-02-28-16-54-36-484.png|width=249,height=158!If I dump the file using od -c i see no content!image-2019-02-28-16-55-40-767.png!Hope this additional information helps!
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-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title
Glenn Herbert commented on JENKINS-56249
Re: userContent *zip* (all files in zip) stopped working at 2.164
Wadeck Follonier: I cannot try using the WAR from JENKINS-56114 as this is a production system. I will try to bring up a new jenkins and try it. To answer your other questions:
we are using the escape hatch -Dhudson.model.DirectoryBrowserSupport.allowSymlinkEscape=true
we are NOT using docker, just running the jenkins windows service
userContent has a mix of files, folders, and directory junctions (symlinks)
The build logs have no real information in them as it was a silent failure, because the zip was empty. The gradle code used was
def f = new File("$buildOutput/staging.zip") if (!f.exists()) { new URL('http://myJenkins:8080/userContent/archive/components/Staging/zip/staging.zip').withInputStream{ i -> f.withOutputStream{ it << i }} } copy
Unknown macro: { from zipTree(f.getAbsolutePath()) into("$buildOutput/config/") }
f.delete()
From the UI, this is the Staging folder (this is not the actual folder used but shows the problem): If i then click on the (all files in zip), the Staging.zip file gets generated but its only 1KB And if its opened with 7zip the file is empty If I dump the file using od -c i see no content Hope this additional information helps!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert updated an issue Jenkins / JENKINS-56249 userContent *zip* (all files in zip) stopped working at 2.164 Change By: Glenn Herbert Attachment: image-2019-02-28-16-55-40-767.png 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-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert updated an issue Jenkins / JENKINS-56249 userContent *zip* (all files in zip) stopped working at 2.164 Change By: Glenn Herbert Attachment: image-2019-02-28-16-54-36-484.png 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-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert updated an issue Jenkins / JENKINS-56249 userContent *zip* (all files in zip) stopped working at 2.164 Change By: Glenn Herbert Attachment: image-2019-02-28-16-53-48-739.png 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-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert updated an issue Jenkins / JENKINS-56249 userContent *zip* (all files in zip) stopped working at 2.164 Change By: Glenn Herbert Attachment: image-2019-02-28-16-52-19-863.png 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-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert updated an issue Jenkins / JENKINS-56249 userContent *zip* (all files in zip) stopped working at 2.164 Change By: Glenn Herbert When using the (all files in zip) functionality starting at 2.164, either from the UI or URL (https:/myjenkins/userContent/* * zip* * /image.zip), the resulting image.zip has no content. This has silently broken our builds, which utilize this functionality to retrieve certain content. Downgrading jenkins.war to 2.163 restores the functionality. 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-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Glenn Herbert created an issue Jenkins / JENKINS-56249 userContent *zip* (all files in zip) stopped working at 2.164 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-22 16:17 Environment: Windows 2008 R2 Enterprise, Jenkins 2.164+ Labels: zip core http Priority: Major Reporter: Glenn Herbert When using the (all files in zip) functionality starting at 2.164, either from the UI or URL (https:/myjenkins/userContent/zip/image.zip), the resulting image.zip has no content. This has silently broken our builds, which utilize this functionality to retrieve certain content. Downgrading jenkins.war to 2.163 restores the functionality. Add Comment
[JIRA] (JENKINS-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Glenn Herbert edited a comment on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo Similar situation. All defined nodes have a Tool Location set for (Git) Default. Works at 3.9.1, but fails at 3.9.2. It's almost as if its ignoring Tool Locations. 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-55827) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Glenn Herbert commented on JENKINS-55827 Re: Git Plugin 3.9.2 cannot clone remote repo Similar situation. All defined nodes have a Tool Location set for (Git) Default. Works at 3.9.1, but fails at 3.9.2. 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-54869) Multibranch project truncates cloudbees folder workspace paths
Title: Message Title
Glenn Herbert updated an issue
Jenkins / JENKINS-54869
Multibranch project truncates cloudbees folder workspace paths
Change By:
Glenn Herbert
With recent updates, the branch API plugin appears to truncate the cloudbees folder workspace paths. For example, we relocate the Jenkins workspace in the config.xml using{code:java} D:/builds/workspace/${ITEM_FULLNAME}{code} Our jobs are within multiple folders, ie ProjectBlue/Developer. This has always resulted in a build workspace at a well known location. For example, with a multibranch project *client_developer*, running a job from branch *APS-1137*, that location would be:{code:java}D:/builds/workspace/ProjectBlue/Developer/client_developer/APS-1137{code} However, with the latest update to branch api 2.1.1, we are seeing truncation of the path to:{code:java}D:/builds/workspace/eloper_client_developer_APS-1137{code} I see that a bunch of work lately has been dealing with slashes, percents, et.al. in workspace paths (JENKINS-38706,[JENKINS-30744,[JENKINS-39251]), but I cannot find one that exactly matches the issue described. The workspaces.txt file shows this truncation:{noformat}1: ProjectBlue/Developer/client_developer/9X_DotNetTool2: r_client_developer_9X_DotNetTool3: ProjectBlue/Developer/client_developer/APS-11374: eloper_client_developer_APS-11375: ProjectBlue/Developer/client_developer/APS-1145-Apr6: er_client_developer_APS-1145-Apr{noformat} Would I see that a bunch of work lately has been dealing with slashes, percents, et.al. in workspace paths (JENKINS-38706,[JENKINS-30744,JENKINS-39251), but I cannot find one that exactly matches the issue described.It would be nice to have some way to override or disable this truncation, restoring functionality of the full path, as this affects a great deal of downstream jobs that expect well known paths.
Add Comment
