[AC-2985] The builder need to add write permission to files copied from the project resources directory
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2011-08-31T18:31:09.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Studio, Titanium SDK & CLI |
| Labels | acl, build, builder.py, chmod, permissions |
| Reporter | Rob Gabbard |
| Assignee | Tony Guntharp |
| Created | 2011-08-30T05:57:27.000+0000 |
| Updated | 2016-03-08T07:47:59.000+0000 |
Description
Some source control systems (e.g. Perforce) set the file access permissions to Read Only (i.e. r--r--r--, 444). This attributes carries over to the files that are copied to the build folders which causes numerous issues as subsequent builds attempt to overwrite those files. The builder scripts should modify the permissions on the newly created build files and add write permission for the owner.
Rob You should exclude all files in the build folder from your VCS. I am closing as invalid, although feel free to reopen if I have misunderstood. Thanks
My build folder is not in my VCS. The issue is that my VCS sets files to read-only at check-in (as many do). When those files are copied to the build directory by builder.py, they retain their read-only state. The next build you do after that fails because builder.py is trying to overwrite a read only file.
Closing due to inactivity.