teamcity

How do I include full PartCover results with TeamCity 5?

由 时间秒杀一切 提交于 2019-12-03 07:38:15
问题 I'm trying to get PartCover reports to generate correctly in TeamCity 5.0. When I click the Code Coverage tab in the build details, the reports are empty. I'm using the sln2008 build agent and my PartCoverage settings are as follows: Include Patterns: [*]* Report XSLT: C:\Program Files\PartCover .NET 2.3\xslt\Report By Assembly.xslt=>ByAssembly.html C:\Program Files\PartCover .NET 2.3\xslt\Report By Class.xslt=>ByClass.html Bonus points if you can describe how to include those reports (or

TeamCity dotCover report path for Sonar

由 流过昼夜 提交于 2019-12-03 07:30:22
问题 I'm trying to integrate the sonar analysis into by TeamCity build process. I have a NUnit build step which runs my unit tests and then runs dotCover for the coverage. My next step is the sonar-runner. The configuration that currently exists is; gallio.mode=dotCover, sonar.gallio.mode=reuseReport but I also need sonar.gallio.reports.path. Does anybody know the path to the dotCover report generated in the the previous step? 回答1: I couldn't find a way to do this using the built in NUnit runner.

Making TeamCity Version Match .NET Assembly Version

由 a 夏天 提交于 2019-12-03 07:16:53
问题 Right now our assemblies have a version number like 2.0.831.0. As I understand it, that's major version, minor version, date and build number. If I make a change and build again on the same day it's 2.0.831.1, 2.0.831.2 etc. My TeamCity build number format is simply 2.{0} where {0} is an auto incremented number that just goes on forever (2.195, 2.196 etc). How do I make TeamCity look exactly like the assembly version? We want to be able to associate the Change Log with the assembly version so

How do I securely configure a CI server to digitally sign binaries?

由 做~自己de王妃 提交于 2019-12-03 07:12:02
问题 There are many sites that explain how to run signtool.exe on a .pfx certificate file, which boil down to: signtool.exe sign /f mycert.pfx /p mypassword /t http://timestamp.server.com \ /d "My description" file1.exe file2.exe I have a continuous integration CI process setup (using TeamCity) which like most CI processes, does everything: checks out source, compiles, signs all .exes, packages into an installer, and signs the installer .exe. There are currently 3 build agents, running identical

How to I configure TeamCity build with Mocha?

由 匆匆过客 提交于 2019-12-03 06:59:19
I have a project that I am setting up through teamcity for CI. The project itself is a nodejs application and it includes test written in mocha, which we cover through jscoverage. In the build configuration I'm setting up I have 3 build steps which occur on checkin. call jscoverage.exe against the folders in my project that I'm covering. call mocha to run the test against the jscovered files from step 1 and output to the html-cov reporter move the generated coverage.html report into a public web directory to browse later. The build currently fails on step 2: mocha" is not present in directory

Change port for TeamCity web server

由 梦想的初衷 提交于 2019-12-03 06:27:28
问题 I installed TeamCity and got it working against my project. However, I have since realized that I don't want it the administration page to be configured on port 80. I'm going to have other websites on that server that I want on the default port. How do I change the configured port? I wandered around the configurations a bit and looked through the administration settings but couldn't figure it out. 回答1: The port number can be edited in the <TeamCity home>/conf/server.xml file, line <Connector

TeamCity Nuget install build step not working with multiple sources, one of them TC's private NuGet feed

由 谁说胖子不能爱 提交于 2019-12-03 06:23:48
I receive the following error in NuGet Install build step when setting sources to TeamCity's NuGet server: Step 1/4: NuGet install (NuGet Installer) (3s) [15:11:19][Step 1/4] scan: Searching for nuget.config files [15:11:19][Step 1/4] install: Installing NuGet packages for packages.config (3s) [15:11:19][install] NuGet command: C:\TeamCity\buildAgent\tools\NuGet.CommandLine.2.2.0.nupkg\tools\NuGet.exe install C:\TeamCity\buildAgent\work\a4b9de5be22a981\packages.config -OutputDirectory C:\TeamCity\buildAgent\work\a4b9de5be22a981\packages -Source http://localhost:9090/guestAuth/app/nuget/v1

WebDeploy with MSBuild Not Deploying from TeamCity

由 ≯℡__Kan透↙ 提交于 2019-12-03 06:15:21
I am trying to use MSDeploy to deploy an MVC project to the server using TeamCity. When I do this on my computer in powershell, using the following command: msbuild.exe .\mvc.csproj /p:PublishProfile=DevServer /p:VisualStudioVersion=11.0 /p:DeployOnBuild=True /p:Password=MyPassword /p:AllowUntrustedCertificate=true It builds the project and deploys it to the server (info defined in the DevServer publish profile) perfectly. The output shows an MSDeployPublish section at the end, in which I see text like Starting Web deployment task from source... and then with rows telling me what files are

Building .NET Core 1.0 RC2 app on the build server

由 狂风中的少年 提交于 2019-12-03 05:58:35
I've updated my app from DNX, ASP.NET 5 RC1 to ASP.NET Core 1.0 RC2. Locally it builds and runs fine. On the build server, I don't have Visual Studio installed, and the build fails with: error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk. I did install the: .NET Core SDK for Windows . Trying to install the VS 2015 tooling preview fails with: What would be the correct setup to build .NET Core 1.0 RC2 app on the build

Create changelog artifact in TeamCity

由 六月ゝ 毕业季﹏ 提交于 2019-12-03 05:57:04
问题 Is there a simple way to have TeamCity include a text or html change-log as one of its output artifacts? Perhaps I need to go down the route of having msbuild or some other process create the change log but as TeamCity generates one for every build, I'm wondering if there is already a simple way to access it as an artifact and include it in the artifact paths directives so that it can be part of a release package. 回答1: Yes, the change-log is accessible as a file, path to this file is in the
订阅 teamcity