Hello folks! In conjunction with the 6.2 Service Fabric release, we updated the Azure Jenkins plugin for Service Fabric to work with the existing Azure Credentials plugin. The Service Fabric Jenkins plugin can now use Azure credentials (Azure Service Principal or MSI) added to the Jenkins credential store for authenticating your Service Fabric cluster. Furthermore, we added pipeline support for the Service Fabric plugin to enable you to use config-as-code to deploy your applications. Jenkins pipeline syntax is a common and recommended way to set up your Jenkins and we are excited extend this functionality to the Service Fabric plugin.
To accomplish this, add the appropriate credential through the Azure Credentials plugin. Next, when configuring your Jenkins job, you can choose the target Service Fabric cluster through the Azure credentials plugin instead of setting the Service Fabric management endpoint. This is ideal for production CI/CD (Continuous Integration & Continuous Deployment) where you will want to use service principles to lock down access to certain Service Fabric clusters. The existing deployment method using the Service Fabric management endpoint still exists and is recommended for development and test environments due to its ease of use.
The diagram below describes each step that occurs when a Jenkins job is triggered. Note that a Docker image containing the necessary plugins installed is available to quickly set up a Jenkins environment and use this pipeline (link at the bottom of post).
To learn more about the improvements and try out Jenkins with Service Fabric, please see the following links: