[
https://issues.apache.org/jira/browse/BUILDR-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721073#action_12721073
]
Daniel Spiewak commented on BUILDR-287:
---------------------------------------
I vote +1 on this. There are some advantages to using /tmp (safer failures,
*better* performance on some systems), but I don't think the advantages are
sufficiently ubiquitus. Is there any way to make this configurable perhaps?
That way, we could still satisfy the one or two people who actually need this
functionality.
> buildr should download temporary files to the destination folder, not the
> temp directory
> ----------------------------------------------------------------------------------------
>
> Key: BUILDR-287
> URL: https://issues.apache.org/jira/browse/BUILDR-287
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.3.4
> Reporter: Ittay Dror
> Fix For: 1.3.5
>
>
> when downloading artifacts, BuildR first downloads to a temporary file in the
> temporary directory (/tmp) and then moves the file to the repository location
> (Generic#download in transports.rb).
> In many unix systems, /tmp is a separate mount from /. This creates two
> drawbacks:
> 1. if there is not enough space in /tmp, the download fails (this happens to
> us many times, and during a nightly build)
> 2. moving files between partitions is actually copy and delete
> If instead, BuildR will download the file to the directory in the repository
> and then rename to the actual file name, these problems will be solved.
> The fix is to use
> Tempfile.open File.basename(target), File.dirname(target)
> When creating the temporary file for download
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
