Deploy: Service Fabric Compose Deploy

Last Update: 6/6/2017

| Team Services |

Deploy a Docker-compose application to a Service Fabric cluster.

This task deploys an Azure Service Fabric application to a cluster according to the settings defined in the compose file.

Prerequisites

NOTE: This task is currently in preview and requires a preview version of Service Fabric that supports compose deploy. See https://docs.microsoft.com/azure/service-fabric/service-fabric-docker-compose.

Service Fabric

  • This task uses a Service Fabric installation to connect and deploy to a Service Fabric cluster.

  • Azure Service Fabric Core SDK on the build agent.

Arguments

Argument Description
Cluster Connection The Azure Service Fabric service endpoint to use to connect and authenticate to the cluster.
Compose File Path Path to the compose file that is to be deployed. Can include wildcards and variables. Example: $(System.DefaultWorkingDirectory)/**/drop/projectartifacts/**/docker-compose.yml. Note: combining compose files is not supported as part of this task.
Application Name The Service Fabric Application Name of the application being deployed. Use fabric:/ as a prefix. Application Names within a Service Fabric cluster must be unique.
Registry Credentials Source Specifies how credentials for the Docker container registry will be provided to the deployment task:
Azure Resource Manager Endpoint: An Azure Resource Manager service endpoint and Azure subscription to be used to obtain a service principal ID and key for an Azure Container Registry.
Container Registry Endpoint: A Docker registry connection endpoint. If a certificate matching the Server Certificate Thumbprint in the Cluster Connection is installed on the build agent, it will be used to encrypt the password; otherwise the password will not be encrypted and sent in clear text.
Username and Password: Username and password to be used. We recommend you encrypt your password using Invoke-ServiceFabricEncryptText (Check Password Encrypted). If you do not, and a certificate matching the Server Certificate Thumbprint in the Cluster Connection is installed on the build agent, it will be used to encrypt the password; otherwise the password will not be encrypted and sent in clear text.
None: No registry credentials are provided (used for accessing public container registries).
Deploy Timeout (s) Timeout in seconds for deploying the application.
Remove Timeout (s) Timeout in seconds for removing an existing application.
Get Status Timeout (s) Timeout in seconds for getting the status of an existing application.
Control options See Control options

Also see: Service Fabric PowerShell Utility

Q&A

Do I need an agent?

You need at least one agent to run your build or release. Get an agent.

I can't select a default agent queue and I can't queue my build or release. How do I fix this?

See queues.

I use Team Foundation Server on-premises and I don't see some of these features. Why not?

Some of these features are available only on Visual Studio Team Services and not yet available on-premises. Some features are available on-premises if you have upgraded to the latest version of TFS.

Help and support