Azure云服务与现有ccproj配置文件的持续集成 [英] Azure Cloud Service continuous integration with existing ccproj profile

查看:382
本文介绍了Azure云服务与现有ccproj配置文件的持续集成的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

如何使用我们的Cloud Project中的个人资料发布设置继续进行集成?





使用默认 TfvcContinuousDeploymentTemplate.12.xaml ,发布将忽略我的一些配置文件设置。它不使用正确的存储帐户,并始终发布到Staging环境。



以下是我的开发发布配置文件的设置:





这是我们构建定义的当前状态:





部署设置路径听起来像是正确的,但它是 $ c> 2。构建> 5.高级> MSBuild参数。


How do I get continuous integration to work using publish settings from a profile in our Cloud Project?

When using the default TfvcContinuousDeploymentTemplate.12.xaml, the publish ignores some of my profile settings. It doesn't use the correct storage account and always publishes to the Staging environment.

Here are the settings for my Development publish profile:

Here is the current state of our build definition:

"Path to Deployment Settings" sounds like it would be correct but it is only for Azure Websites.

How do I get this to publish using all profile settings as specified in my .azurePubxml file?

解决方案

CI template TfvcContinuousDeploymentTemplate.12.xaml will not use your publishing profile. Relevant settings (deployment slot, storage account name, ...) are configured in 6. Deployment > Deployment > Windows Azure Deployment Environment

/p:TargetProfile=Development specifies service configuration only (selects correct .cscfg file), not a publishing profile.

If you need to configure additional features like for example remote debugging, you will have to add additional msbuild parameters in 2. Build > 5. Advanced > MSBuild arguments.

这篇关于Azure云服务与现有ccproj配置文件的持续集成的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆