TeamCity 2017.2 artifact directory permissions changed?
After upgrading to 2017.2 running on a linux box, newly created artifact directories (.BuildServer/system/artifacts/**) have changed permissions and no longer reflect the umask in affect. Specifically the group write permissions are missing.
When logged in as the user that the server runs under, creating of directories using the shell work as expected.
Has the teamcity code changed in this regard?
Please sign in to leave a comment.
Got the same issue. Why TeamCity ignores umask at creating artifacts? Now we need to use some dirty tricks with ACL or setuid :(
Created issue https://youtrack.jetbrains.com/issue/TW-53337