Our build environment pumps out the latest build onto a Windows file share in a predefined location. We get file lock problems when remote users open and maintain folders and files on that read-only file share, and this causes our builds to break. Is there any technology that can solve this for us?
I've thought about
- Enabling only WebDav and disabling SMB (can you?)
but none of those candidate solutions seem like a great fit so far.
To clarify, assume the path to the "latest build" is \server\share\path\Latest and only the build server has write access. Someone has opened a command prompt or an msi file somewhere in the "Latest" folder. Now the build server is done and needs to purge all content from the folder before copying in all the newly built pieces. No can do.
If an SMB share had had symbolic link support or some idea of transactions like NTFS or being able to rename "open" directories like HFS - but nope.
And putting all binaries in Sharepoint Document folders as has been suggested elsewhere seems like a crappy idea as well because of the data volume. I'd rather go for a WebDAV-only share that mounts like a file system but behaves like a web site.