teamcity

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: I came across an interesting issue. I want to build nuget packages with Teamcity. I did set up the configuration which is really straight forward (Good job JetBrains!) However I am not able to run it on one of our build agents. The agent does pass the agent requirements for the configuration, but next to it's name the following is shown: not allowed to run this configuration My question: Why? On the agent configuration parameters page I have Nuget as possible configurations: teamcity.tool.NuGet.CommandLine.2.8.2.nupkg D:\BuildAgent\tools

We are setting up a Team City build server. On previous VS 2008 projects a full version of Visual Studio has been installed on the build server. We are now starting a VS 2010 project. Is it possible to run MSTest tests on the Team City build server without installing Visual Studio? Download the Visual Studio Agents 2010 ISO: http://www.microsoft.com/en-us/download/details.aspx?id=1334 Mount/Extract the files and copy them to the agent server Run AutoRun and select to install Microsoft Visual Studio Test Agent 2010 Install using the default settings Cancel out of the "configuration" dialog (you

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: 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. 回答1: 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

I am trying to figure out how to make TeamCity run my MSTests. I have setup a build step using the following parameters: Path to MSTest.exe: %system.MSTest.10.0% List assembly files: Projects\Metadude. .Tests\bin\Debug\Metadude. .Test.dll MSTest run configuration file: Local.testsettings However when this step runs, it does not execute any tests. This is the output from the log: [02:13:49]: Step 2/2: Run Unit Tests (MSTest) [02:13:49]: [Step 2/2] Starting: "D:\Program Files (x86)\TeamCity\buildAgent\plugins\dotnetPlugin\bin\JetBrains.BuildServer.NUnitLauncher.exe" #TeamCityImplicit [02:13:49]:

I have a few tests that need to be fed with external data from excel files. The files are included in the test project, and in Visual Studio, I have edited the test settings file (Local.testsettings) to deploy the data files. This makes it work fine i VS. We are, however, also running continous integration with TeamCity, and in TeamCity this doesn't work. My data files are unavailable to the test. Seems that the tests are run from a temporary folder named "C:\TeamCity\buildAgent\temp\buildTmp\ciuser_AS40VS6 2009-12-11 09_40_17\Out", and the data files are not copied there. I have tried

I'm trying to run a custom command in my MSBuild file; it basically runs 'git log -10' and stores that commit info into a text file. The problem is, when I try to run the build, it errors saying "fatal: Not a git repository". So I checked TeamCity's work directory for my project, and there is no .git directory! Why doesn't TeamCity create the .git directory when it clones the repository? Is there a way to enable this? edit: TeamCity version is 7.1.2; I'll try updating to 8.0.1 to see if there is an option available for this. xofz I changed the VCS checkout mode from server to "automatically on

I have set up a build step on TeamCity,as described here , to do automatic release deployments to our test server. But it is not using the latest nuget packages that was build in TeamCity. Use Case : Teamcity will create nuget package with version 1.0.0.9, all the dlls that is in the package is the correct version, and the Release in Octopus, that was deployed has got the same version number , but the packages that octopus uses is of an earlier package eg 1.0.0.5. I have specified the --force parameter on the build step so it should use the latest packages but it is not. If I manually create a