Visual Studio Team Services,连续部署和WebJobs [英] Visual Studio Team Services, continuous deployment and WebJobs

查看:83
本文介绍了Visual Studio Team Services,连续部署和WebJobs的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是否有人管理过使用Visual Studio Team Services RELEASE任务建立有效的部署管道?我能找到的所有信息似乎都基于Nuget发布包,该包直接从源头获取其参数.我正在尝试在具有多种环境的适当发行版工作流中进行这项工作,从开发人员开始进行质量检查以生产管道等.

Has anyone managed so set up a working deploy pipeline using Visual Studio Team Services RELEASE tasks? All the info I can find seem to be based on the Nuget publishing package which takes its parameters directly from the source. I am trying to get this working in the proper release workflow with multiple environments, dev to QA to prod pipeline etc.

在那种情况下,该工具似乎并不适用-至少,我无法找出VSTS中powershell发布任务实际上填充app_data文件夹并设置计划的参数的任何组合.

The tooling does not seem to be in place for that scenario - or at least, I cannot figure out any combination of parameter where the powershell publish task in VSTS actually populates the app_data folder and sets up the schedule.

坦白说,我完全被困住了.

Frankly I am completely stumped.

推荐答案

您可以使用"Azure Web App部署"任务来部署WebJob,并使用

You can use "Azure Web App Deployment" task to deploy your WebJobs and use CRON expression to set up the schedule.

类似的问题供您参考:如何使用vNext在VSO中通过CI部署Webjob

A similar questions for your reference: How to deploy a webjob through CI in VSO with vNext

这篇关于Visual Studio Team Services,连续部署和WebJobs的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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