We're in the process of moving away from Visual Studio's web publish into Azure DevOps and require some clarity on how parallel jobs are "consumed", or an alternative way to quickly deploy our application to multiple destinations.
Our web application has a single code-base and is published into 15 separate clients' hosting areas (all on Azure App Services), each with their own configuration file transform during the final deployment process, e.g.:
Currently the process is working well on Azure DevOps' "free" account, but it takes around one hour to deploy to each client hosting environment as the processes run in a queue (
Deploy Customer 1 →
Deploy Customer 2 → ...).
Yesterday to streamline the process and get the deployments done asynchronously we purchased three "Parallel Jobs" from the billing area. Deployment was indeed much quicker as three ran in parallel. However, when they were finished there were no parallel jobs available in our account.
The terminology in the Learn portal talks about monthly resources, so we had assumed that the parallel job agents were a one-month purchase (buy once/use many in that month).
If they are consumed immediately upon completion then according to the pricing calculator, if have a weekly release and use 15 parallel jobs then that will cost me over £2,000 per month (£35.34 * 15 * 4) which seems unbelievably expensive for a short time saver.
Can anyone please clarify the situation, or suggest an alternative method for deploying asynchronously?