teamcity

Web Application Build Error: The CodeDom provider type Microsoft.VisualC.CppCodeProvider could not be located

时光总嘲笑我的痴心妄想 提交于 2020-03-17 05:09:12
问题 I'm building/packing a web application in a build server, and it fails with the following message: ASPNETCOMPILER error ASPCONFIG: The CodeDom provider type "Microsoft.VisualC.CppCodeProvider, CppCodeProvider, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" could not be located. This is the build server environment: Windows Server 2008 R2 Standard TeamCity 8.0.4 .NET 4.5 Windows SDK for Windows 7 and .NET 4 Windows SDK for Windows 8 and .NET 4.5 Portable Class Library

Web Application Build Error: The CodeDom provider type Microsoft.VisualC.CppCodeProvider could not be located

折月煮酒 提交于 2020-03-17 05:08:30
问题 I'm building/packing a web application in a build server, and it fails with the following message: ASPNETCOMPILER error ASPCONFIG: The CodeDom provider type "Microsoft.VisualC.CppCodeProvider, CppCodeProvider, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" could not be located. This is the build server environment: Windows Server 2008 R2 Standard TeamCity 8.0.4 .NET 4.5 Windows SDK for Windows 7 and .NET 4 Windows SDK for Windows 8 and .NET 4.5 Portable Class Library

在生成服务器上找不到Microsoft.WebApplication.targets。 您有什么解决方案?

落花浮王杯 提交于 2020-02-27 05:39:45
尝试在构建服务器上构建我的项目会给我以下错误: Microsoft (R) Build Engine Version 4.0.30319.1 error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\TeamData\Microsoft.Data.Schema.SqlTasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. error MSB4019:

Powershell with Git Command Error Handling - automatically abort on non-zero exit code from external program

扶醉桌前 提交于 2020-02-25 04:18:21
问题 I use Git to deploy my web application. So in Teamcity I prepare my application (compilation, minify JS and HTML, delete unused files, etc...) and then I have a Powershell build step : $ErrorActionPreference = "Stop" git init git remote add origin '%env.gitFolder%' git fetch git reset --mixed origin/master git add . git commit -m '%build.number%' git push origin master But if an exception throw, the script continue (even if I set $ErrorActionPreference = "Stop" ) and the build is successful.

Powershell with Git Command Error Handling - automatically abort on non-zero exit code from external program

﹥>﹥吖頭↗ 提交于 2020-02-25 04:18:10
问题 I use Git to deploy my web application. So in Teamcity I prepare my application (compilation, minify JS and HTML, delete unused files, etc...) and then I have a Powershell build step : $ErrorActionPreference = "Stop" git init git remote add origin '%env.gitFolder%' git fetch git reset --mixed origin/master git add . git commit -m '%build.number%' git push origin master But if an exception throw, the script continue (even if I set $ErrorActionPreference = "Stop" ) and the build is successful.

Parallel Cypress tests on TeamCity

喜欢而已 提交于 2020-02-01 09:24:46
问题 We currently have a repo containing 24 integration/*.js files. We are successfully running Cypress tests via our TeamCity CI workflow, however, I am unable to get the tests to run in parallel. By way of configuration, we have the repo/tests wired up to an org in dashboard.cypress.io. Along with the dashboard key, we are calling Cypress in a TeamCity build step via npm run with the following configs in our package.json scripts{} : "cypress:run:qa": "cypress run -c cypress.qa.json --record -

Can TeamCity branches concept be applied to Subversion with Build Chains?

爱⌒轻易说出口 提交于 2020-01-25 20:24:26
问题 We had some success using the branches concept of TeamCity in subversion by pointing to tags like mentioned here https://stackoverflow.com/a/6875151/2416394 although we are aware that this is primary for DVCS like git. We've extended the answer from the link by providing a project parameter %Tag% which became part of the checkout rule. So our SVN Root is http://myserver/svn/tags/ and the checkout rule is +:%Tag%=>. Each time we checkout a new tag is added as "branch" and build the source,

TeamCity配置笔记

柔情痞子 提交于 2020-01-24 22:59:54
1.编译sln 2.发布网站 3、重复代码检测 4、代码分析 5.单元测试&覆盖率测试 查看代码覆盖率 7.代码签入时自动触发编译 8.通知 1.在teamcity安装目录中找到TrayNotifierInstaller.msi安装打开 2.相关设置 单元测试失败时,右下角弹出 9.备份&还原配置 还原: 1. 停止TeamCity服务 2.清空 TeamCity Data Directory/config(备份config/database.properties到其他目录) 和 TeamCity Data Directory/system 目录。 3.命令行进入目录TeamCity\bin. maintainDB restore -F <absolute path to TeamCity backup file> -A <absolute path to TeamCity Data Directory> -T <absolute path to the database.properties file of the target database> 来源: https://www.cnblogs.com/miku/p/4419436.html

How to deploy Angular 4 App using Teamcity ?

╄→гoц情女王★ 提交于 2020-01-24 20:49:46
问题 I am using TeamCity for CI and build for my Angular App. As of now i have configured the project such that On each commit the build is triggering and generating the package successfully. Now i have requirement that on each successful build, the generated build package should get deployed on a server(we call it artifacts(e.g: https://serverurl.com). Can anybody please guide how to configure my project to achieve this? 回答1: TeamCity contains an integrated lightweight builds artifact repository.

How to deploy Angular 4 App using Teamcity ?

别来无恙 提交于 2020-01-24 20:49:12
问题 I am using TeamCity for CI and build for my Angular App. As of now i have configured the project such that On each commit the build is triggering and generating the package successfully. Now i have requirement that on each successful build, the generated build package should get deployed on a server(we call it artifacts(e.g: https://serverurl.com). Can anybody please guide how to configure my project to achieve this? 回答1: TeamCity contains an integrated lightweight builds artifact repository.