In the release pipeline, there will be one job available called Manage IIS Website, which is used for IIS web application management.
Here we can configure our instance name in the field of Website name, Physical path will be the root folder path of the instance, Use Action as Create or Update.
Now, the IIS Website configuration is done, if we now run the CD(Release) pipeline out instance should point out to a new folder created on the name if the release number.
Sharing the view of IIS Website settings post Release pipeline.
Here we can see the physical path of our website is changed to the path we gave in the field description. So, the files present on that folder path will be now the root files of our website which are the latest artifacts which just been deployed to the folder.
This is how we can configure the IIS Website in a job provided in the CD(Release) pipeline.
By following these steps and automating the deployment and management of your IIS website in a release pipeline, you can achieve a reliable and repeatable deployment process, reduce human error, and ensure that your website is always up-to-date and configured correctly in various environments.
Cloud-based eCommerce platforms are the most in demand right now. The global retail sales increased approximately to USD 4.2 trillion during the pandemic. The share of eCommerce as of 2021 globally in the total retail sales is 21%.Read More