You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Jared Robinson (JIRA)" <ji...@apache.org> on 2008/09/02 22:05:44 UTC
[jira] Updated: (BUILDR-143) Upload to a file:// path needs ability
to specify permissions
[ https://issues.apache.org/jira/browse/BUILDR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jared Robinson updated BUILDR-143:
----------------------------------
Description:
When uploading an artifact to a file:// repository URL, the permissions on the artifact are rw by owner, but unreadable by anyone else. When I deploy to a samba share, this is a problem, because no one else can read the artifact. I've tracked it down to the use of Tempfile in transports.rb. Tempfile always creates a file with permission 600. If I add the following code, everything works as expected:
temp.chmod(0644)
I'd prefer it if the artifact was created using my default umask, and then allow me to override it with an option :permissions so that I can specify what file mode I want.
This could be related to issue BUILDR-23
was:
When uploading an artifact to a file:// repository URL, the permissions on the artifact are rw by owner, but unreadable by anyone else. When I deploy to a samba share, this is a problem, because no one else can read the artifact. I've tracked it down to the use of Tempfile in transports.rb. Tempfile always creates a file with permission 600. If I add the following code, everything works as expected:
temp.chmod(0644)
It may be appropriate to add an option :permissions so that users can specify what file mode they want. This could be related to issue BUILDR-23
> Upload to a file:// path needs ability to specify permissions
> -------------------------------------------------------------
>
> Key: BUILDR-143
> URL: https://issues.apache.org/jira/browse/BUILDR-143
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.2.10
> Environment: Linux(RHEL 4) with a samba mount point
> Reporter: Jared Robinson
>
> When uploading an artifact to a file:// repository URL, the permissions on the artifact are rw by owner, but unreadable by anyone else. When I deploy to a samba share, this is a problem, because no one else can read the artifact. I've tracked it down to the use of Tempfile in transports.rb. Tempfile always creates a file with permission 600. If I add the following code, everything works as expected:
> temp.chmod(0644)
> I'd prefer it if the artifact was created using my default umask, and then allow me to override it with an option :permissions so that I can specify what file mode I want.
> This could be related to issue BUILDR-23
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.