Delete/Redeploy Azure Websites at specific times within a TeamCity and Octopus Deploy CI/CD pipeline
Many clients request that specific environments be only available certain times during a day.
This is often due to the high cost associated with keeping environments that are not in use.
The problem here can be divided into two.
1. How do we make the environment unavailable?
2. How do we make the environment available once more?
Microsoft will charge Azure services per compute time. Meaning that even if you stop your Azure Website it will still incur costs. This is the crux of the problem. It means that we have to deploy and delete the deployment of the Websites in order to minimise cost effectively.
Now if we have our project building, testing and deploying in a TeamCity and Octopus deploy pipeline. Ideally the Undeploy and Re-Deploy should be tunneled through the appropriate stage in the pipeline.
The reason why we should do this is to ensure that redeployment goes through the same processes as a normal deployment, and that environment states (such as version number, failed/passed) all have one source of truth - The CI/CD pipeline.
This solution assumes:
- That TeamCity is setup
- Octopus Deploy is setup and deploying. Either with custom PowerShell scripts or the build-in Octopus ones.
There are three steps to the solution which I will show below.
- Write a PowerShell script that calls the Octopus REST API that simply re-deploys the latest release.
- Write a PowerShell script that deletes the deployment on the environments.
- Set triggers on TeamCity and call these scripts.
Step 1 - Deploy script
I assume that you’ve already got Octopus deploying successfully.
The next step is to create a PowerShell script that calls the Octopus API and deploys your application from Octopus. The logic is:
- Find the environment
- Get the current deployed release on that specific environment
- Redeploy this release
An example of this script can be found here.
Basically this script ‘redeploys’ the latest release on a given environment. The reason why we have parametised the environment is that many organisations have more that one testing environment they need taken down during non-operational hours.
Step 2 - Undeploy/delete script
As I stated previously, we need to actually delete an environment in this case, because of the way Azure has priced its services.
We opted to use the Azure cmdlets to do this. An example can be found here.
Step 3 - TeamCity triggers
Now, the final step is to setup your TeamCity triggers to execute the above scripts at the appropriate times.
Typically, the deploy script (from step 1) will be executed in the morning and the updeploy/delete script (from step 2) will be executed in the evening.
What I prefer doing is having two build configurations for each of the above. A deploy configuration and an undeploy.
Setup each of the build configuration. Then go to build steps and add the powershell script.
Then go to triggers and add a ‘schedule trigger’.
And that’s it! You’re done.
1. Create deploy script using Octopus API.
2. Create delete deployment script using Azure cmdlets.
3. Use TC as script runner and schedule scripts.