teamcity-9.0

Run a build step on a specific branch only

我是研究僧i 提交于 2019-12-21 12:19:15
问题 I have a build configuration containing two build steps "Build" and "Deploy". This build configuration is using a Git VCS and is configured to run all branches. Let's assume that I currently have two branches "master" and "Feature in Development". I want to divide the "Deploy" step into two. "Deploy Production" and "Deploy Beta". The "Deploy Production" step should only be executed when the master branch was changed and is currently building. Is there a built in possibility to do that or do I

change server url from localhost

巧了我就是萌 提交于 2019-12-13 15:25:27
问题 I installed teamcity 9.1 on mac os. I can access teamcity via http://localhost:8111/ . I can change port in file TeamCity/conf/server.xml by changing <Connector port="8111" protocol="org.apache.coyote.http11.Http11NioProtocol" . But how can I change server url e.g. http://localhost:8111/ to http://teamcity.test:8111/ I tried changing in server.xml from <Engine name="Catalina" defaultHost="localhost"> But after I start teamcity as ./runAll.sh start it stills can access from http://localhost

TeamCity - setParameter value available to Build Feature

孤人 提交于 2019-12-12 18:10:40
问题 I've a little PS script to write this TC integration command: ##teamcity[setParameter name='AssemblyVersionString' value='1.0.46.48' Which sets a Configuration Parameter which appears to run fine in the logs. The Configuration Parameter is defined at the project level and has a default value. Eventually I want to use the AssemblyInfoPatcher but for testing, I've added a Build Feature to tag the git repo but its tagging with the default value. Are changes during the build supposed to be

Is there a way to force a default value for a parameter in TeamCity and not lose it once a different value has been set?

走远了吗. 提交于 2019-12-12 10:49:03
问题 I have a parameter for which I'm showing a prompt. I've set a default value for it and that works fine. What doesn't work, however, is that if I choose to enter a different value when running the build, then on the next build this value automatically becomes the new default value, so to say. I'd like the default value to always be fixed and if you enter a different value in the field, then that value will be used just for this build (and the next build will fallback to the fixed, default

How to build a project in teamcity after multiple other builds have finished and not trigger the dependency chain?

时光毁灭记忆、已成空白 提交于 2019-12-07 20:45:01
问题 My questions is related to Trigger subsequent build once after multiple parallel builds in TeamCity but I have hit a problem so posting it here. Below is my setup. I am trying to create a chain so that when I run A, the complete chain runs. A ( Root project) - B ( Snapshot dependent on A + Finish Build trigger on A) -( Snapshot dependent on B) Aggregation project. A ( Root project) - c ( Snapshot dependent on A + Finish Build trigger on A) - ( Snapshot dependent on C)Aggregation project. The

TeamCity NuGet package build for different .NET Frameworks

孤者浪人 提交于 2019-12-07 07:30:46
问题 I've been doing updates to .NET Framework targeted versions of projects updating to latest .NET (4.6.2). Some of these projects are NuGet packages, built in TeamCity 9.0.2. I've use the steps in this guide to create multiple build configurations for different .NET Framework version as some of the projects I haven't updated to 4.6.2 reference the NuGet packages. So I am trying to get TeamCity to use these build configurations to output the various Net40, Net45, Net46 and Net462 versions so

How to build a project in teamcity after multiple other builds have finished and not trigger the dependency chain?

流过昼夜 提交于 2019-12-06 11:28:12
My questions is related to Trigger subsequent build once after multiple parallel builds in TeamCity but I have hit a problem so posting it here. Below is my setup. I am trying to create a chain so that when I run A, the complete chain runs. A ( Root project) - B ( Snapshot dependent on A + Finish Build trigger on A) -( Snapshot dependent on B) Aggregation project. A ( Root project) - c ( Snapshot dependent on A + Finish Build trigger on A) - ( Snapshot dependent on C)Aggregation project. The snapshot dependency does not really do anything ( there is no snapshot, I am using a dummy build config

TeamCity with BitBucket Cloud Commit Status Publisher. 404 Errors

筅森魡賤 提交于 2019-12-06 09:34:42
问题 I'm having problems getting the commit status publisher to work. Details: TeamCity 9.1 Commit Status Publisher Plugin version: snapshot-20160523141816 Bitbucket Cloud git repository type on bitbucket.org VCS Settings: Configured to use the private key auth (w/ uploaded key) Multiple branches configured. Not using VCS Labeling No PUSH URL specified (should be failing back to FETCH URL, right?) Commit Status Publisher Settings: I've experimented with these settings, neither email addresses nor

Pass argument with quotes to PowerShell script via TeamCity

空扰寡人 提交于 2019-12-05 19:15:05
We're calling a PowerShell script via TeamCity. We want to pass a parameter which contains quotes, e.g.: Build step : PowerShell Script file : foo/bar/my.ps1 Script arguments : -MyParam "%system.MyParam%" Where system.MyParam is set to <xml><elem attr="value"></elem></xml> . Unfortunately, this fails with: Cannot process argument transformation on parameter MyParam . Cannot convert value " <xml><elem " to type " System.Xml.XmlDocument ". Error: "Unexpected end of file while parsing Name has occurred. Line 1, ..." Anybody knows how to correctly pass double quotes? What I've tried so far and

Teamcity fails to merge automatically

让人想犯罪 __ 提交于 2019-12-05 16:42:55
问题 Given there are master and dev git branches, a git repository is hosted on the Github and TeamCity 9.0.1 installed as a CI server. The teamcity build project is configured to use github repository as a VCS root with refs/heads/master set as a default branch. The desired behavior is to run auto-merge from master to dev when the build is successful. So I add an Automatic merge build feature as specified here with the following settings: Watch builds in branches => Branch filter: +:master Merge