teamcity

问题 The AssemblyInfoPatcher build feature isn't working. Some files are patched and some are not. Assembly file version was specified, but couldn't be patched in file D:\TeamCity\Agent\buildAgent\work\6afd998e316c631f\La\Di\Da\Properties\AssemblyInfo.cs. Is necessary attribute missing? I thought it was because it was 1.0.* since one of the failed files had this format, and one of the successful ones had the default 1.0.0.0 format, so I changed the attribute to 1.0.0.0 across the entire solution

问题 When teamcity executes an MSBuild step, the build log has a collapsible/expandable hierarchy. I have one big build step that runs a powershell script and the resulting build log is large and takes a lot of time to load. Is there a way to make teamcity split a single build step into it's many smaller steps instead of just one giant text file? 回答1: There is no way to split the build step into multiple steps in the log, but you can create nested collapsible blocks, as described in this answer.

问题 I have some C# performance tests, basically running two different methods and checking that one runs much faster than the other. When I run them locally in NUnit, one of the tests runs ten times as fast as the other, so I've got an NUnit test that uses Stopwatch to check that it is at least twice as fast (in case of regression). But when I run the tests in TeamCity, the fast method is only about 1.5 times as fast as the slow one? I would expect hardware differences to have some effect, but

问题 I am using the TeamCity Visual Studio runner. I want to add a setting that is not accessible from Visual Studio. /Property:FileAlignment=4096 I typed that directly into the build step "Command line parameters." The build log shows the error: MSBuild command line parameters contains "/property:" or "/p:" parameters. Please use Build Parameters instead. I don't understand how to provide this to MSBuild from TeamCity and get rid of this warning! 1. Which kind of parameter should I use? There are

问题 I seem to be unable to install a build agent on our TeamCity 5.1.2 build server that is compatible with a VS2010 (sln) build configuration. Under "Build Runners", the following runners are listed: Ant: Runner for Ant build.xml files Duplicates finder (.NET): C# and VB duplicate code finder Command Line: Simple command execution And under "Compatible configurations", the project I've configured to build with the Visual Studio 2010 (sln) build runner is listed under "Incompatible configurations

问题 I have very simple maven descriptor which defined some properties: <?xml version="1.0"?> <project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <properties> <it.port>8080</it.port> </properties> </project> I can override it.port property with command: $ mvn -Dit.port=8181 verify But following command doesn't work as expected: $ MAVEN_OPTS="-Dit

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . Duplicate: Continuous Integration Cruise Control .NET alternatives? I'm planning to start Continuous Integration where I work. I used

问题 I understand the HTTPClient and GET process. What I'm trying to find here is the correct URL/syntax to make this work with Team City. I've been trying to get this to work using the examples at RestDocumentation However, they all require a buildId. This is a distinct build number which changes with each build. I've tried several combinations with buildId=lastSuccesful but I just can't seem to get the syntax correct. I have been able to create a link that successfully downloads a specific build

问题 I'm new to TeamCity and we have a number of common projects under source control that are then referenced directly within relevant projects i.e.: Common branches tags trunk CommonProject CommonProject.csproj Common.sln ProjectX branches tags trunk ProjectX.sln As a result, the reference to "CommonProject.csproj" in "ProjectX.sln" is something along the lines of ....\Common\trunk\CommonProject\CommonProject.csproj which is fine within our development enviroments but when it comes to TeamCity

问题 I have a Gradle task to upload jacoco coverage to TeamCity (following TeamCity documentation here: Importing JaCoCo coverage data to TeamCity): task uploadJacocoTestReport { doLast { println "##teamcity[jacocoReport dataPath='build/jacoco/jacocoTest.exec' " + "includes='com.mypackage.*' " + "classpath='build/classes/main']" } } If I use Gradle 3.5 , TeamCity build is able to display CodeCoverage report in the build log. But when I switch to Gradle 4.5 , the Code Coverage section no longer