executable flag getting lost when TeamCity unzips artifacts

Hey,

To optimize the artifact dependencies, we zip our artifacts up in our buildscript, and use the teamcity syntax:

ZippedForTeamCity.zip!**

to have it be unpacked for us by teamcity.  It turns out that when teamcity unpacks (on macosx), it does not perserve the executable flags.

When we download the zip manualy, and unzip ourselves, the flags are perserved.  When we check the workingcopy that the teamcity buildconfig uses

that needs these artifacts, it has them unzipped in its incoming artifacts folder without the executable bit set.

Is this a known bug?

Bye, Lucas

1 comment
Comment actions Permalink

Sorry for delay. No, this is not a known issue. Please submit a bug report.

0

Please sign in to leave a comment.