[JIRA] [durable-task-plugin] (JENKINS-27152) Store bourneshell control files outside of workspace
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27152 Store bourneshell control files outside of workspace Change By: Jesse Glick Labels: api docker robustness workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-27152) Store bourneshell control files outside of workspace
Title: Message Title Jesse Glick commented on JENKINS-27152 Re: Store bourneshell control files outside of workspace It was also found that CLI Git checkouts using SSH private keys create temporary files which must be put in a standardized location. Seems there needs to be some shadow directory created on demand for any workspace where temporary files may be placed which are only intended to be accessed by build steps running in that workspace. credentials-binding should also be updated to use such a location for its temporary files. The lack of this API was just never noticed until Image.inside came along, because plugins simply assumed that build steps using a workspace could also access arbitrary files created on the same computer by the slave agent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-27152) Store bourneshell control files outside of workspace
Title: Message Title Jesse Glick commented on JENKINS-27152 Re: Store bourneshell control files outside of workspace Agreed. A subfolder of the slave root would probably be safest. A little trickier than merely changing the directory location, though, since the volumes parameter here must be adjusted to include that location, meaning some kind of API from durable-task by which docker-workflow could find that temporary directory. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-27152) Store bourneshell control files outside of workspace
Title: Message Title A C commented on JENKINS-27152 Re: Store bourneshell control files outside of workspace This is a very significant flaw with this plugin. The temporary-directory solution in the workspace is still far less than ideal, this really should use a system-provided temporary directory. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-27152) Store bourneshell control files outside of workspace
Vincent Latombe updated JENKINS-27152 Store bourneshell control files outside of workspace Change By: Vincent Latombe (26/Feb/15 8:39 PM) Summary: Store bourneshell control file files outside of workspace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
