teamcity

Has anyone had any success with running StyleCop from TeamCity? I know StyleCop supports a command line mode, however i am not sure how this will integrate into the report output by TeamCity. I've checked out this plugin found here: https://bitbucket.org/metaman/teamcitydotnetcontrib/src/753712db5df7/stylecop/ However could not get it running. I am using TeamCity 6.5.1 (latest). I don't know how familiar you are with MSBuild, but you should be able to add a new Build Step in TC 6 and above, and set MSBuild as the build runner, and point it to a .proj file which does something similar to the

I have been studying MSBuild as I have the need to automate my development shop's builds. I was able to easily write a .BAT file that invokes the VS command prompt and passes my MSBuild commands to it. This works rather well and is kinda nifty. Here is the contents of my .BAT build file: call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64\vcvars64.bat" cd C:\Sandbox\Solution msbuild MyTopSecretApplication.sln /p:OutputPath=c:\TESTMSBUILDOUTPUT /p:Configuration=Release,Platform=x86 pause ^ This works well but I now have the need to use the MSBuild task for TeamCity CI. I have

I need to recover/reset the admin password for JetBrain's TeamCity . I have full RDP access to the server so no problems there. It's just been 2 months since we used it so now I have forgotten my login - my usual ones don't work. It is setup without a database at the moment, so was hoping the usernames would just be in a file somewhere, but no luck finding it so far. Sebastien Lachance In case none of those works, see http://sebastienlachance.com/post/Resetting-TeamCity-Password.aspx . Open a command prompt and go to \webapps\ROOT\WEB-INF\lib folder. Now type the following : ..\..\..\..\jre

I have a Visual Studio solution which includes a Test project having Selenium Tests. (I already have a compilation build triggered by version control checkin (Mercurial)) But I want to have a separate (nightly) Build Configuration which runs the Selenium tests, ideally under MSTest. I assume I need Selenium Server for this? If so, what's the best way to fire it up before running the tests? Should I do this from the MSBuild script or use a Build Step from Team City itself? Do I need to fire up Cassini\WebDev.WebServer first of all so the following can run: selenium = new DefaultSelenium(

Our buildserver (TeamCity, much recommended), runs our a whole bunch of testsuites on our finished c++ program. Once in a whole, a test causes our program to crash, often bringing up a VisualStudio dialog offering me to JustInTime debug the crash. The dialog stops the buildserver from progressing. Instead of the build marked as failed, it just hangs. I've turned off the Just In Time debugging feature in VisualStudio, but when it's turned off, you still get a message "Couldn't JustinTime Debug this, you can turn it on in the options". Does anybody know of a way to ensure that any unhandled

I've got an existing C# 4 project which I've checked the test coverage for by using TestDriven.Net and the Visual Studio coverage feature, i.e. Test With -> Coverage from the context menu. The project contains some code I don't want covered, and I've solved that by adding the [ExcludeFromCodeCoverage] for those types and methods. We've just upgraded TeamCity to 6.0.3, and I've added dotCover coverage to the NUnit build step. I've managed to remove coverage for external assemblies such as NHibernate in the "Filters" section (by explicitly state the assemblies for which I want coverage), but I'm

I am doing prepare release through Temcity using release-plugin I got below error [10:46:19][Step 2/3] [INFO] Executing: /bin/sh -c cd /home/tcagent/buildAgent/work/860f91e0ad4abff2 && git push https://username:****@testurl.com:8081/scm/myrepo/my-project-name.git/**buildConfName** refs/heads/release/release-name:refs/heads/release/release-name [10:46:19][Step 2/3] [INFO] Working directory: /home/tcagent/buildAgent/work/860f91e0ad4abff2 [Step 2/3] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) on project **my-project-name**: Unable to commit