Since Azure errors aren't always so verbose, I've decided to give the user the possibility to trigger runs with --debug option enabled.
I'm running the following command in Jenkins using the azure-cli-plugin:
azureCLI commands: [[exportVariablesString: '', script: "az group deployment create --name jenkins-ci-deployment --resource-group ${resource_group_name} --template-file ${arm_file_path} --parameters ${parameters_file_path} ${debug_command}"]], principalCredentialId: env.subscription
I've noticed that when debug is enabled, even if the deployment correctly terminates, the only way to stop the job is to manually abort it.
Since Azure errors aren't always so verbose, I've decided to give the user the possibility to trigger runs with --debug option enabled. I'm running the following command in Jenkins using the azure-cli-plugin:
azureCLI commands: [[exportVariablesString: '', script: "az group deployment create --name jenkins-ci-deployment --resource-group ${resource_group_name} --template-file ${arm_file_path} --parameters ${parameters_file_path} ${debug_command}"]], principalCredentialId: env.subscriptionI've noticed that when debug is enabled, even if the deployment correctly terminates, the only way to stop the job is to manually abort it.