[英]Team Services deploy to on-premise Service Fabric without exposed endpoint
We have a Service Fabric cluster on-premise and would like to deploy code to it from Visual Studio Team Services. 我们有一个内部的Service Fabric群集,希望从Visual Studio Team Services对其部署代码。 We use this cluster for testing and it does not have an endpoint exposed to the outside world.
我们使用此群集进行测试,并且没有端点暴露于外界。 It is only accessible internally from inside our network.
它只能从我们的网络内部进行访问。
From inside Team Services the normal way to deploy a Service Fabric application is with the "Service Fabric Application Deployment" task. 在Team Services内部,部署Service Fabric应用程序的通常方法是使用“ Service Fabric应用程序部署”任务。 This task requires a "Cluster Connection" parameter, or link to the Service Fabric Service endpoint that Team Services can access.
此任务需要“群集连接”参数,或链接到Team Services可以访问的Service Fabric Service端点。 On this cluster I can't provide an endpoint to the outside world, so this method won't work.
在此群集上,我无法提供外部端点,因此此方法无效。
Is there a good, accepted way of accomplishing this? 是否有一种良好的,可以接受的方式来实现这一目标? I'm considering looking at having an Agent on one of the Service Fabric nodes that can run a PowerShell script as part of the build process.
我正在考虑在一个Service Fabric节点上安装一个代理,该代理可以在构建过程中运行PowerShell脚本。 I can kick off a PowerShell script on the node as part of the build process.
作为构建过程的一部分,我可以在节点上启动PowerShell脚本。 If I could retrieve the artifacts from Team Services with this script I believe the rest of the release would be relatively straightforward.
如果我可以使用此脚本从Team Services检索工件,那么我相信该版本的其余部分将相对简单。
Is this a good line of thought, or is there a more straightforward way to deploy to Service Fabric from Team Services without exposing an endpoint? 这是一个好的思路,还是有一种更直接的方法可以从Team Services部署到Service Fabric而无需暴露端点?
We have the same set up and using VSTS. 我们具有相同的设置并使用VSTS。 We set up a On-Prem agent pool where agent is within our network.
我们建立了一个本地代理池,其中代理位于我们的网络中。 The agent is hook with VSTS so build and release can be trigger from VSTS.
该代理与VSTS挂钩,因此可以从VSTS触发构建和发布。 Agent have access to the artifact on VSTS and can download it for deployment.
代理有权访问VSTS上的工件,并可以下载它进行部署。 The different might be we set up a service fabric end point instead of using powershell.
不同之处可能是我们设置了服务结构端点,而不是使用Powershell。
Its a very simple set up and works well for us.Good luck 它的设置非常简单,对我们来说效果很好。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.