sln2005 builder not cleaning?

I'm not sure if this is a bug or not - not sure what to expect.

We had a problem last night with our build, and it was only failing in
TeamCity's agent. A dev got on the agent, into its working folder and
opened the .sln file in Visual Studio right from there to tinker around.
In doing so, he did a Debug build, TeamCity is configured to do a
Release build.

After resolving the problem, we still had Debug output folders leftover,
and got some duplicate test assemblies that were run. So, I realized the
problem, and marked the build to run clean the next time out. But on the
next build, none of the Debug output folders were removed - it looked
like the Agent re-used the same working folder and everything.

So ... what should I expect clean to do? (maybe it just does a clean
pull but won't remove artifact folders?)

3 comments

Chris,

What TeamCity version do you use?

What checkout rules and resulting directory structure do you have? Where is output directory located?

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Yegor Yarko (JetBrains) wrote:

Chris,

What TeamCity version do you use?


TeamCity Enterprise Version 3.0.1 (build 6010)

What checkout rules and resulting directory structure do you have? Where is output directory located?


It's probably a little more complicated, but essentially:

app
\--src
\ \--bin (output from Visual Studio - not a folder in source control)
\
\--test
\--bin
\--Debug
\--Release

Note - most of assemblies use the default Debug\Release output folders -
but in some cases we've overridden the defaults and had both
configurations output to the same 'bin' folder.

0

Chris,

Sources clean should delete the directories with the content checked out by TeamCity (these are either checkout directory or the target directories used in the checkout rules). Provided no checkout rules are present and build checkout directory is "app", it should have been deleted.

It seems we will need the agent logs to investigate the issue. If you encounter this again, can you please submit an issue?

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.