teamcity

Karma is failing to launch IE when running under Team City. I can log onto the sever and run the tests from the command line, but IE always fails from Team City: [Step 6/6] INFO [karma]: Karma v0.12.37 server started at http://localhost:9876/ [14:45:09][Step 6/6] INFO [launcher]: Starting browser Chrome [14:45:09][Step 6/6] INFO [launcher]: Starting browser Firefox [14:45:09][Step 6/6] INFO [launcher]: Starting browser IE [14:45:25][Step 6/6] INFO [Firefox 38.0.0 (Windows 7 0.0.0)]: Connected on socket KeIupP7qx6Dn9ghM0KsX with id 75681035 [14:45:32][Step 6/6] INFO [Chrome 43.0.2357 (Windows 7

I'm currently using JMeter to load test some application, I used the duration assertion and I set it to, let's say 200, when the load time exceeds 200, the Request in the Result Tree becomes Red for it is an error. Problem is, when i run the same test with TeamCity, it is always marked as success , even if all the Requests have failed . What you are looking at is the summary. You need to add a listener to your project, that saves results to a file. Then you need to have Teamcity read that file and assert the result. Teamcity is just telling you "Ehhhhh the script you wanted me to run worked".

I have the following set-up in TeamCity 7.1.3: Project A Build & Deploy A Test A (Quick) Test A (Slow) Test A (Very Slow) Project B Build & Deploy B Test B (Quick) Test B (Slow) All of the tests for A depend on 'Build & Deploy A' and all of the tests for B depend on 'Build & Deploy B'. The dependencies are all snapshot dependencies with the following settings: Do not run new build if there is a suitable one Only use successful builds from suitable ones Run build on the same agent All of the tests have VCS triggers. The slow tests only run when particular folders in source control are changed.

We have a build step to build a solution with about 70 projects using the Visual Studio (sln) as the runner type. We are able to successfully build other projects that are not supported by MSBuild, such as a vdproj file and office plug-ins by doing this. However, it apparently does not work for SSDT/SSRS projects. I have made sure the latest version of SSDT is installed to Visual Studio, and Visual Studio 2015 is directly on the build server. rptproj is not supported by MSBuild and cannot be built Is there any thing else I need to do to get these to build correctly? I have read about some

I've just committed some code changes to my repository and all of a sudden (after weeks of being fine). The TC build starts failing as it fails to download the NuGet package for Microsoft.Bcl.Build.1.0.6. I ended up having to manually copy the contents of the packages directory to the TC build location which utterly defeats the point of NuGet. What can I check to get to the root cause of this? Everything about NuGet is enabled in the solution for getting packages. I've blogged about this issue at http://sedodream.com/2012/12/24/SlowCheetahBuildServerSupportUpdated.aspx . To summarize NuGet

Here's an interesting problem that really has me scratching my head. I have a project that's being built in TeamCity. It's been working fine until a developer added a resource file to one of the projects with some strings for another locale. He's added the .resx file under the Properties folder next to the default one. Here's the error message from the build log: C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(2105, 9): error MSB3091: Task failed because "AL.exe" was not found, or the correct Microsoft Windows SDK is not installed. The task is looking for "AL.exe" in the "bin"