teamcity

TeamCity: Prevent 2 builds from running simultaneously

这一生的挚爱 提交于 2019-12-06 19:28:01
问题 I don't want Build Config A and Build Config B to run at the same time. This is because they share the same resource which cannot be accessed simultaneously. However each build config is run by a separate agent so it is possible for them to run simultaneously. Instead I would like one build config, when triggered, to wait for the other to finish if it is running. For example if Build Config B begins to run but Build Config A is already running, then B would wait until A finishes and then B

Test projects not reading app.config in TeamCity -> NUnit phase

扶醉桌前 提交于 2019-12-06 18:16:29
问题 Well we are facing a strange problem with JetBrains TeamCity induced unit tests on our main project where tests from few library projects are failing regularly. Apparently, it's not reading the config file (coming from app.config and nicely stored in project -> bin -> debug -> projectName.dll.config). Hints or tips on what could be the real issue would be highly appreciated. 回答1: I've got the same problem and wasted a couple of hours to figure out what the problem is. In our case, the NUnit

TeamCity Vs BuildForge

早过忘川 提交于 2019-12-06 16:54:38
We are currently using TeamCity and planning to move on to BuildForge because of organizational needs/constraints. I want to do a feature comparison on TeamCity and BuildForge. Could anyone please help me on this. As I could find comparison of BuildForge with other CI tools such as Hudson, CruiseControl only. I would use the other comparisons as a baseline (especially the Hudson one which will be quite close), and basically create a matrix of features you care about, and see which tools do what. You may ask IBM for their break-down. A great list of features for CI tools in general (with data

Ant and Junit: no xml report being generated

99封情书 提交于 2019-12-06 13:16:28
I'm very new to ant and junit. I need junit to create an xml output so I can integrate with team city. The tests run just fine, but I'm not getting any output in the directory that I'm specifying. I'm running on windows 7. I have junit.jar and ant-junit.jar in my ant_home/lib directory. here is my build xml target: <target name="onlyjunit-sikuli" description="Execute All sikuli tests"> <delete dir="${automated}/results/sikuli"/> <mkdir dir="${automated}/results"/> <mkdir dir="${automated}/results/sikuli"/> <junit printsummary="yes" showoutput="yes" fork="true" forkmode="once"> <jvmarg value="

TeamCity Ant Junit 2 reports skipped as out-of-date

放肆的年华 提交于 2019-12-06 12:29:39
I'm setting up TeamCity to do automated builds when I commit something to develop. The problem being that on attempting to do a build I'm getting a reports skipped as out-of-date message. Here's my build.xml <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- WARNING: Eclipse auto-generated file. Any modifications will be overwritten. To include a user specific buildfile here, simply create one in the same directory with the processing instruction <?eclipse.ant.import?> as the first entry and export the buildfile again. --> <project basedir="." default="build" name="RNS-Reader-v0.1">

Team City build fail not returning fail code

断了今生、忘了曾经 提交于 2019-12-06 10:47:51
I have a powershell script that runs Invoke-MsBuild on TeamCity. During a build I saw a "WARNING: FAILED to build" one of the projects. However teamcity at the end said the build was successful. How can I force TC to exit with an error code or at least report the build failed. Here is part of the build script. Write-Host "Attempting to build $SolutionPath" $buildSucceeded = Invoke-MsBuild -Path $SolutionPath -MsBuildParameters $MSBuildParams -BuildLogDirectoryPath "$BuildPath\Logs" -KeepBuildLogOnSuccessfulBuilds TeamCity isn't very good at catching and reporting exceptions thrown from

dotnet core deployment to azure app service using teamcity

﹥>﹥吖頭↗ 提交于 2019-12-06 08:47:19
I have a dotnet core app. I am building a pipeline in teamcity. and once the teamcity detects the change in the cource code, It downloads the source code runs dotnet restore dotnet build and copies the content in the output folder to Azure app service. I believe to run the app i need to run the command dotnet nameoftheprojectdll.dll but how can I run this command on the app service. and I need to run this command as part of a build script. The Short Answer You need to use the dotnet publish command to package your application for IIS deployment, and copy that output (not the output from dotnet

Deploying a asp.net website using team city

落爺英雄遲暮 提交于 2019-12-06 08:30:30
How to deploy a web site project, which does not have any project file. we are trying to automate build and deployment using team city. i am able to successfully build the project, but not able to deploy the web site. MsDeploy supports deployment of WebSites via contentPath provider: msdeploy -verb:sync -source:contentPath=WebSite\Deploy,computername=localhost -dest:auto... Just change WebSite\Deploy to your actual path in your agent working directory, where is your builded website for deployment. 来源: https://stackoverflow.com/questions/14956108/deploying-a-asp-net-website-using-team-city

How can I pass MSDeploy-style parameters to MSBuild via the commandline?

你离开我真会死。 提交于 2019-12-06 08:20:25
问题 I am setting up TeamCity to deploy our Website Project application (using a *.wdproj) and Web Deploy application to IIS. I have a build configuration that uses MSBuild.exe with the MSDeployPublish to build and then deploy the application. We now want to get the application to deploy to multiple target environments, therefore need a way to supply different settings based on the target environment. I have added a parameters.xml file to the Web Deployment Project, and have verified that the

Increment the build number automatically

强颜欢笑 提交于 2019-12-06 07:07:00
问题 I have two projects in solution. One is version 3.0.0.* and the other is 2.0.0.*. I build my solution on Team City using an MSBuild script. How can I inject the build number portion of the version string into the AssemblyVersion attribute leaving the major.minor.patch as defined at dev time. To put it another way I want to manually control major.minor.patch (and the majors will differ across libs in the solution) but auto increment the build number. 回答1: TeamCity will automatically manage the