[5725] Incomplete source gets to the agent

Hello, I've came to the office today to find that two of my configs didn't
build...the error reported was that the .sln file could not be found.

While looking into the work directory of the build agent I saw an
incomplete copy of the source code to be built, tried using the 'Clean
Sources' button on the agent page, tried removing the work directory
completely, tried commiting another file to the repository...no luck.

Any ideas? I'm using SVN...

Regards,
Pablo

--


Money talks, but it is not obliged to tell the truth.

Pablo Montilla
www.odyssey.com.uy

2 comments

Pablo Montilla wrote:

Hello, I've came to the office today to find that two of my configs
didn't build...the error reported was that the .sln file could not be
found.

While looking into the work directory of the build agent I saw an
incomplete copy of the source code to be built, tried using the 'Clean
Sources' button on the agent page, tried removing the work directory
completely, tried commiting another file to the repository...no luck.

Any ideas? I'm using SVN...


I've had problems like this with CVSNT (so none of this may be
applicable), and it turned out to be a problem with our server bailing
out during the pull, but no real error message turning up in the output.
Some generic suggestions:

1) Make sure and look over the complete TeamCity build log, there might
be a useful nugget of error output in there somewhere.

2) See if you can duplicate the action you're doing manually with SVN on
either the build server/agent (whichever is doing the pulling) or your
own machine. Our particular problem was really only noticeable when
doing a complete clean pull, which most of our developers weren't doing
as they already had pulled most of the files, so no one really noticed
the problem.

Also, if SVN has any sort of debug logging you might find some help in
there. TeamCity has some debug logging you can turn on in one of its
config files, but I don't know if it'll give you much more on the
interaction with SVN.

0

On Tue, 23 Oct 2007 12:01:00 -0200, Chris Morris
<chris.morris@einstruction.com> wrote:

Pablo Montilla wrote:
I've had problems like this with CVSNT (so none of this may be
applicable), and it turned out to be a problem with our server bailing
out during the pull, but no real error message turning up in the output.
Some generic suggestions:

>

1) Make sure and look over the complete TeamCity build log, there might
be a useful nugget of error output in there somewhere.

>

2) See if you can duplicate the action you're doing manually with SVN on
either the build server/agent (whichever is doing the pulling) or your
own machine. Our particular problem was really only noticeable when
doing a complete clean pull, which most of our developers weren't doing
as they already had pulled most of the files, so no one really noticed
the problem.

>

Also, if SVN has any sort of debug logging you might find some help in
there. TeamCity has some debug logging you can turn on in one of its
config files, but I don't know if it'll give you much more on the
interaction with SVN.


Thanks for your answer, I really don't know what the problem was, but I
resorted to the shotgun approach to fix it, and deleted the sourcesCache
directory from TeamCity's data directory. That made TeamCity do a complete
checkout (163Mb of sources and data), and all is in fine working condition
again...=)

I did check all the logs in the build agents (none were working) and the
server, but did not find anything that could be causing problems. I also
did a checkout to a client machine to see if SVN was causing the problem,
but couldn't reproduce the problem...

Anyway, the server is building again, so I'll give it a rest and continue
coding...;)

Regards,
Pablo


--


-- Hundred-and-one symptoms of being an internet addict
194. Your business cards contain your e-mail and home page address.

Pablo Montilla
www.odyssey.com.uy

0

Please sign in to leave a comment.