teamcity

pycharm debug console unreadable because of teamcity

☆樱花仙子☆ 提交于 2019-12-05 03:23:56
Since a few days my pycharm debug console is systematically polluted by teamcity infos, e.g. when i want to print out a variable value, the following will be displayed: >>> df ##teamcity[testStdOut timestamp='2017-11-02T15:55:00.670' flowId='test_pricing_36_weight_provider.TestPricing36WeightProvider.test_add_weights' locati... Any hint how to deactivate this teamcity thing ? user48956 This is a PyCharm/IntelliJ bug. PyCharm replaces stdout with its own object. They do a bunch of screwing around with objects that get printed, resulting in: some object are not printed to the prompt some

TeamCity NUnit build step failing although all tests pass

梦想的初衷 提交于 2019-12-05 03:14:22
I'm setting up TeamCity to run some NUnit tests, TeamCity reports that all the test pass but it reports the build as a fail with the error message 'New build status is : : NUnit error, {build.status.text}'. Digging in to the build log I can see that there's a failure to load the program under test, here's the reported error; [Step 2/2] NUnit error running tests in 'C:\TeamCity\buildAgent\work\f73bb9cce36ccd59\ProjectName.Web\ProjectName.BrowserTests\obj\Release\MyProject.BrowserTests.dll' assembly Loading assembly is compiled for v4.0.30319, MSIL NUnit runner runtime is v4.0.30319, x86 System

Attribute filter syntax for code coverage in TeamCity

送分小仙女□ 提交于 2019-12-05 02:46:59
Anyone knows the syntax for excluding code from coverage in Teamcity? I am using the ExcludeFromCodeCoverageAttribute on certain methods and want those excluded. It works well in Visual Studio but I don't understand how to get the same behavior in TeamCity. The Field I am trying to configure is located in MsTest -> .Net Coverage -> Attribute Filters: I have tried this: -:ExcludeFromCodeCoverageAttribute and this -:ExcludeFromCodeCoverage After trying out a few variations this worked: -:System.Diagnostics.CodeAnalysis.ExcludeFromCodeCoverageAttribute Make sure you add this filter inside

How do I make a TeamCity build appear in the TFS Build Explorer?

别等时光非礼了梦想. 提交于 2019-12-05 02:43:09
We are using TFS 2010 for source control and project management, and TeamCity 6.0 for performing builds and build reporting (CI and daily deployments for testers). Setting up TFS source labeling in TeamCity to match the build number was very straightforward, but I cannot find a way to link this back to TFS Build Explorer. We want link these to be able to assign bugs to particular builds through TFS for the daily tester deployment builds. I don't know if you can, at least without some heavy VSX work or direct manipulation of the database, get the TeamCity builds to show up in the TFS Build

Wix heat.exe with project harvesting type

给你一囗甜甜゛ 提交于 2019-12-05 02:30:17
I'm using the lastest version of Wix 3.5 and I'm trying to generate a fragment file using heat.exe. The command line is : "%WIX%\bin\heat.exe" project "MyProj.csproj" -pog Binaries -pog Content -suid -directoryid INSTALLLOCATION -ag -template fragment -out "Files.wxs" The prolem I'm having is that the assemblies my project is depending uppon are missing from the generated file. Is this the intended behaviour ? How can I add them ? Should I use the dir harvesting type ?! How to remove *.pdb or *.vshost.exe then ? I want to use it with CI Server (TeamCity) edit : I tried -pog Satellites and

MSBUILD : error MSB1008: Only one project can be specified in teamcity

微笑、不失礼 提交于 2019-12-05 02:25:32
I am trying to run msbuild with teamcity. I have a batch file and I pass into it parameters and the build works. When I try to run through teamcity I get error below [13:24:46][MSBuild output] Start MSBuild... [13:24:46][MSBuild output] 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe' '"@C:\TeamCity\buildAgent\work\999585556854a516\Build\Default.msbuild.teamcity.msbuild.tcargs" C:\TeamCity\buildAgent\work\999585556854a516\Build\Default.msbuild.teamcity' [13:24:46][MSBuild output] working dir = 'C:\TeamCity\buildAgent\work\999585556854a516' [13:24:46][MSBuild output] Microsoft (R)

如何基于k8s快速搭建TeamCity(YAML分享)

自作多情 提交于 2019-12-05 02:19:44
前言 最近有朋友基于之前的博客《Docker最全教程之使用TeamCity来完成内部CI、CD流程(十七)》搭建TeamCity时出现了一些问题,由于平常比较忙,没有及时答复,非常抱歉。 这里分享下基于本地k8s集群(云端k8s服务注意使用云盘或者其他存储)搭建TeamCity的相关Yaml的配置文件,注意使用“kubectl apply -f <路径>”命令执行。 服务端YAML定义 apiVersion: apps/v1beta1 kind: Deployment metadata: labels: app: teamcity name: teamcity spec: replicas: 1 #实例数量 revisionHistoryLimit: 2 #保留的历史记录数,设置为0将清理部署的所有历史记录,无法回滚 strategy: type: Recreate #更新策略为快速更新,即关闭所有实例重新创建 template: #pod模板 metadata: labels: app: teamcity spec: containers: - image: jetbrains/teamcity-server #镜像 imagePullPolicy: Always #拉取策略 name: teamcity ports: #端口列表 - containerPort: 8111

TeamCity + WiX + MSBuild workflow suggestions needed

六眼飞鱼酱① 提交于 2019-12-05 00:02:34
问题 I've been working on the next step of my continuous integration project, which is to get TeamCity to build my application, automatically change the version number of all assemblies, and then create an installer. A little background first: I've been running TeamCity successfully for the past several months, and it builds my configurations and runs my NUnit and NCover tests just fine. I took a little time researching installers -- I have always hated InstallShield and never considered it for my

TeamCity: Prevent 2 builds from running simultaneously

人走茶凉 提交于 2019-12-04 23:29:23
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 would run. I don't think a snapshot dependency will work because that assumes one config has a dependency

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

删除回忆录丶 提交于 2019-12-04 23:28:24
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. Gaspar Nagy I've got the same problem and wasted a couple of hours to figure out what the problem is. In our case, the NUnit plugin was configured to run the tests from: **\*Tests.dll Though this sounds to be OK, it has