Jenkins Plugin to create an Azure Container Service cluster with a DC/OS orchestrator and deploys a marathon config file to the cluster.
Register and authorize your client application.
Retrieve and use Client ID and Client Secret to be sent to Azure AD during authentication.
Refer to
- Download the azure-acs-plugin.hpi file from here
- Within the Jenkins dashboard, click Manage Jenkins.
- In the Manage Jenkins page, click Manage Plugins.
- Click the Advanced tab.
- Click on the Choose file button in the Upload Plugin section and choose the azure-acs-plugin.hpi file.
- Click the Upload button in the Upload Plugin section.
- Click either “Install without restart” or “Download now and install after restart”.
- Restart Jenkins if necessary.
- Within the Jenkins dashboard, Select a Job then select Configure
- Scroll to the "Add post-build action" drop down.
- Select "Azure Container Service Configuration"
- Enter the subscription ID, Client ID, Client Secret and the OAuth 2.0 Token Endpoint in the Azure Profile Configuration section.
- Enter the Region, DNS Name Prefix, Agent Count, Agent VM Size, Admin Username, Master Count, and SSH RSA Public Key in the Azure Container Service Profile Configuration section.
- Enter the Marathon config file path, SSH RSA private file path, and SSH RSA private file password in the Marathon Profile Configuration section.
- Save Job and click on Build now.
- Jenkins will create an Azure Container Service cluster and deploy the marathon file to the cluster upon cluster creation if cluster doesn't exist. Otherwise, the marathon file will be deployed to the existing Azure Container Service cluster.
- Logs are available in the builds console logs.