Team City is by far and away the best CI server out there. Its killer feature for me is the tight integration with IDEs (IntelliJ, Eclipse and VisualStudio). It can show you, for example, when a file you’re editing in the IDE becomes out of date, who changed it and what they changed. You can … Read more
Even if you provide the /Y switch with xcopy, you’ll still get an error when xcopy doesn’t know if the thing you are copying is a file or a directory. This error will appear as “exited with code 2”. When you run the same xcopy at a command prompt, you’ll see that xcopy is asking … Read more
Use msbuild with /nr:false. Briefly: MSBuild tries to do lots of things to be fast, especially with parallel builds. It will spawn lots of “nodes” – individual msbuild.exe processes that can compile projects, and since processes take a little time to spin up, after the build is done, these processes hang around (by default, for … Read more
I had a similar issue using the Chrome driver (v2.23) / running the tests thru TeamCity. I was able to fix the issue by adding the “no-sandbox” flag to the Chrome options: var options = new ChromeOptions(); options.AddArgument(“no-sandbox”); I’m not sure if there is a similar option for the FF driver. From what I understand … Read more
I have worked on and with Continuous Integration tools since the one that spawned Cruise Control (java version). I’ve tried almost all of them at some point. I’ve never been happier than I am with TeamCity. It is very simple to set up and still provides a great deal of power. The build statistics page … Read more
I got it mostly working without a custom msbuild script. Here are the relevant TeamCity build configuration settings: Artifact paths: %system.teamcity.build.workingDir%\MyProject\obj\Debug\Package\PackageTmp Type of runner: MSBuild (Runner for MSBuild files) Build file path: MyProject\MyProject.csproj Working directory: same as checkout directory MSBuild version: Microsoft .NET Framework 4.0 MSBuild ToolsVersion: 4.0 Run platform: x86 Targets: Package Command line … Read more
To check if any module in a project is ‘old’: npm outdated ‘outdated’ will check every module defined in package.json and see if there is a newer version in the NPM registry. For example, say xml2js 0.2.6 (located in node_modules in the current project) is outdated because a newer version exists (0.2.7). You would see: … Read more