We have a project that builds with artifacts from another project. The first project generates two artifacts which are the result of an msbuild step that creates the deploy package for two ASP.NET websites. The second project depends on those two artifacts so that it can deploy the websites.
What I am seeing in TeamCity v7.1.1 on a Windows Server 2012 machine is that one of the deploy packages (Artifact1.zip) is corrupted. If I download that file directly from the project overview page, it is fine and I can extract all of the files without any issue. I ran the website build project and checked the resulting dependencies to make sure they were okay, but for some reason, the deploy project keep complaining that the file is corrupted on download. Has anyone experienced this? I even tried adding the artfiact as a depenency in a different project. It's getting the corrupted file there as well.
Here is the output of the "Check artifact depenencies" button in the Dependencies section of the project configuration. Obviously the names for the projects and files were sanitized for public consumption. Any help would be very much appreciated.
[15:55:39]: Dependency resolving started...
[15:55:39]: Downloading artifacts from: http://builds.mycompany.com
[15:55:39]: Downloading Artifact1.zip from <Application-Web :: Application-Web (Build Sandbox), build from the same chain> to Artifact1\Artifact1.zip;
[15:55:40]: Failed to download artifact dependency <Application-Web :: Application-Web (Build Sandbox), build from the same chain>: java.io.IOException while unpacking archive C:\TeamCity\temp\dep2223960268664773070dep\Artifact1\Artifact1.zip: Truncated ZIP file (jetbrains.buildServer.artifacts.ResolvingFailedException)
[15:55:40]: Downloading Artifact2.zip from <Application-Web :: Application-Web (Build Sandbox), build from the same chain> to Artifact2\Artifact2.zip;
[15:55:41]: <Permits-Web :: Application-Web (Build Sandbox), build from the same chain> Artifact2.zip => Artifact2/Artifact2.zip (5 files unpacked)
[15:55:41]: Failed to resolve 1 of 2 artifact dependencies
[15:55:41]: Dependency resolving finished with errors