CODEWITHSUNDEEP
command-lineteamcity
user1230213
user1230213

Reputation: 1

TeamCIty 6.5.6 build step with Runner Type="Command Line" never completes

I am using TeamCity 6.5.6 to implement a CIT environment. I am trying to add a build step of Runner Type = "Command Line" and trying to executing the following custom cmd script

"C:\Program Files\PreEmptive Solutions\Dotfuscator Professional Edition Evaluation 4.9\dotfuscator.exe" /in:D:\CITTest\bin\CITTest.Lib.dll /out:D:\CITTest\Dotfuscated

But, TeamCity is never able to complete the build step and it seems it is taking forever.

Please note that, the paths and commands mentioned in the script are correct, and, the same command is successfully executed in the command prompt.

I've also tried to execute this script using a batch file from within TeamCity, but, same thing is happening.

Can any one help in this regard?

Thanks

Upvotes: 0

Views: 1329

Answers (3)

Michael Xin
Michael Xin

Reputation: 11

Don't use command line. For some unknown reason, Dotfuscator license checking will fail. If you use MSBuild script, you can try this: http://www.edsquared.com/2007/11/13/Integrating+Dotfuscator+Into+Team+Build+TFS.aspx

Upvotes: 1

Newhill
Newhill

Reputation: 21

Found the same problem with Teamcity 7.1 and Dotfuscator professional edition 4.9. And I tried the administrative TeamCity Build service, it still failed to run. My final action is to import Dotfuscator tasks in MSBuild script and call Dotfuscator task to do obsfucating. It works well even without administrative TeamCity Build service. Please check this link : http://www.edsquared.com/2007/11/13/Integrating+Dotfuscator+Into+Team+Build+TFS.aspx

Upvotes: 0

spacesens
spacesens

Reputation: 11

Had the same issue. Configured the TeamCity Build Agent Service to log on an account with administrative rights. It solved it.

Upvotes: 1

Related Questions