TeamCity screwing up artifacts

Hi,

Recently teamcity is messing up the artifacts sent to an agent for use using the artifact dependency option.  We are copying zip files as artifacts and when the build goes to use one of the artifacts the artifact is in a bad state (didn't get all of the file).  When downloading the file from the UI the artifact is fine.  We did some investigation and checked the artifact in the system artifact.cache directory and it is messed up there as well.  Has anyone run into this?  Jetbrains is this a known problem?  I attached a snapshot of the artifact dependency settings.  I'll be filing a youtrack ticket if I don't hear back.

Thanks,
Jay

screen-capture-109.png

6 comments
Comment actions Permalink

Hello Jason,

That does not seem to be known problem.

What version of TeamCity do you use?
Is this problem seen on one agent only? Or on all of them?

0
Comment actions Permalink

Hi Nikita,

We are using version 6.5.4.  This happens on some agents and doesn't happen all the time.  We mostly use ec2 instances so not sure if that helps in diagnosing.  I'd also like to point out that subsequent builds using the same artifact from the same build id kept having issues until I went and manually deleted the artifact from the system artifact.cache directory on the agent.  Does teamcity pull down a new artifact even though it has it on the agent?  How does it decide it to refresh the artifact it already has?

Let me know if you need more information.

Thanks,
Jay

0
Comment actions Permalink

Hello Jason,

TeamCity agent first tries to use artifact.cache directory, and if artifact is missing, downloads it from build server. Looks like, agent fails to determine that cache content is invalid. I've filed an issue for this: http://youtrack.jetbrains.net/issue/TW-19079

To understand the cause of getting broken archive on the agent, would you please do the following:

On an agent:

- remove the artifact from the artifact.cache directory on the agent
- enable agent debug logging/ For this, see the comments in the  configuration file <agent home>/conf/teamcity-agent-log4j.xml
- after getting error caused by broken artifact, please attach logs here.

0
Comment actions Permalink

Hi Nikita,

The issue is no longer happening and have no idea when it will happen again.  Will turning on debug create really big log files?  The reason I ask is you want this on so when it happens again you have more information right?

Thanks,
Jay

0
Comment actions Permalink

Hello, Jay,

Sorry for the delay.

Turning the debug logs on will increase file size. But logs are "rolling" and won't store more than 4 files at 10Mb each, so you don't have to worry about it using up all the space.
Yes, you are right. I need these logs to see what is happening, how it turns out agent receives broken artifact.

0
Comment actions Permalink

Thanks Nakita,

I'll turn it on and let you know the next time it happens.

Thanks,
Jay

0

Please sign in to leave a comment.