Excellent explanation in simple language in a step-by-step manner, I am able to create a end to end CI/CD pipeline for my project. Thank you very much.
great explanation question: for my virtual machine I have multiple sites... how do I ensure my pipeline is directed to the site I want and not just the default site? any extra steps?
Thanks. For deploying to a specific site, you can use the Website name field in both IIS Web App Manage and IIS Web App Deploy tasks. By default, it's linked to Parameters.WebsiteName which u can find if you click on the stage name above the task list. You can either specify it there or click Unlink all to unlink the parameters and specify it individually on the Task.
You can refer this video for more explanation. Azure DevOps Deployment Groups: Common Questions Answered for Web App Deployment to IIS | OmegaCodex th-cam.com/video/w9KNMCn-59A/w-d-xo.html
Thanks for the great video, there is one query that ,is there any setup for exclude certain files ?for example ,i do not want to deploy my config file to server, i want to exclude that file!
In IIS Web App Deploy Task, we can use Additional Arguments section to mention folders or files to exclude something like shown below example: -skip:objectName=dirPath,absolutePath=wwwroot\\Uploads -skip:objectName=filePath,absolutePath=\\web.config'
How we can create pipeline to deploy on IIS site's subside or subdolder? Also how to stop the site before deployment and starting same after deployment through pipeline?
For deploying to a subsite, you need to change the configuration type under stage name. Click on the stage name and you can find the option configuration type. Select ‘Web Application’ in that option. Then you will see a new field ‘virtual path’ below website name field. Enter the subfolder name here. Also you need to update physical path in manage task and update virtual app in deploy task You can set app offline by enabling ‘Take App Offline’ option in IIS WebApp Deploy Task. This will take your app offline before deployment.
Hello sir, I am trying to create pipeline for on-premise dev-ops account with repository as TFS. I created CI pipeline, created target environment as the same VM under deployment group, but it failed to deploy through release pipeline i created, the error is: ERROR ( message:Configuration error Filename: redirection.config Line Number: 0 Description: Cannot read configuration file due to insufficient permissions ##[error]Process 'appcmd.exe' exited with code '5'. Kindly Help
It could be because the user under which your agent is running doesn't have access to read redirection.config. What is Azure agent service running as? In Windows services and look for the agent, something like Azure Pipelines Agent and check as which user its running
No you don’t. When you install the agent, it connects to the DevOps instance. Thought your local server should be able to access Internet if you are using Az DevOps services.
I get the following error in "Download artifact" step - 2024-02-05T10:44:36.0522456Z ##[error]Failed in getBuildApi with error: Error: unable to verify the first certificate 2024-02-05T10:44:36.1275105Z ##[error]Error: unable to verify the first certificate
It could be an issue with the build pipeline. Make sure you are using the correct task for publishing artifacts. Use Publish pipeline artifact instead of publish build artifacts
Excellent explanation in simple language in a step-by-step manner, I am able to create a end to end CI/CD pipeline for my project. Thank you very much.
Thanks 😊
Thank you very much from Germany
Welcome. ☺️
Thanks sir, very simple explanation
Welcome. Glad it was helpful
Thanks for the info shared, also please make a video on "deploy PHP application on Linux VM using deployment groups.
Thanks for the suggestion. Sure.. will take it upcoming videos
Thanks!
Welcome!
Thank you
great explanation
question: for my virtual machine I have multiple sites... how do I ensure my pipeline is directed to the site I want and not just the default site? any extra steps?
Thanks. For deploying to a specific site, you can use the Website name field in both IIS Web App Manage and IIS Web App Deploy tasks. By default, it's linked to Parameters.WebsiteName which u can find if you click on the stage name above the task list. You can either specify it there or click Unlink all to unlink the parameters and specify it individually on the Task.
You can refer this video for more explanation.
Azure DevOps Deployment Groups: Common Questions Answered for Web App Deployment to IIS | OmegaCodex
th-cam.com/video/w9KNMCn-59A/w-d-xo.html
Thanks for the great video, there is one query that ,is there any setup for exclude certain files ?for example ,i do not want to deploy my config file to server, i want to exclude that file!
In IIS Web App Deploy Task, we can use Additional Arguments section to mention folders or files to exclude something like shown below
example:
-skip:objectName=dirPath,absolutePath=wwwroot\\Uploads
-skip:objectName=filePath,absolutePath=\\web.config'
You can refer this video for more explanation.
Common Questions Answered for Web App Deployment to IIS
th-cam.com/video/w9KNMCn-59A/w-d-xo.html
How we can create pipeline to deploy on IIS site's subside or subdolder?
Also how to stop the site before deployment and starting same after deployment through pipeline?
For deploying to a subsite, you need to change the configuration type under stage name. Click on the stage name and you can find the option configuration type. Select ‘Web Application’ in that option. Then you will see a new field ‘virtual path’ below website name field. Enter the subfolder name here. Also you need to update physical path in manage task and update virtual app in deploy task
You can set app offline by enabling ‘Take App Offline’ option in IIS WebApp Deploy Task. This will take your app offline before deployment.
You can refer this video for more explanation.
Common Questions Answered for Web App Deployment to IIS
th-cam.com/video/w9KNMCn-59A/w-d-xo.html
Mine is stucked at 5:48 , it take time should i wait or there is some issue ? Ok now i get it we have to press enter !!
glad it worked. :)
Hello sir, I am trying to create pipeline for on-premise dev-ops account with repository as TFS. I created CI pipeline, created target environment as the same VM under deployment group, but it failed to deploy through release pipeline i created, the error is: ERROR ( message:Configuration error
Filename: redirection.config
Line Number: 0
Description: Cannot read configuration file due to insufficient permissions
##[error]Process 'appcmd.exe' exited with code '5'.
Kindly Help
It could be because the user under which your agent is running doesn't have access to read redirection.config.
What is Azure agent service running as? In Windows services and look for the agent, something like Azure Pipelines Agent and check as which user its running
I can’t see Development group tool after clicking the pipeline
Which version of Azure Devops are you using ?
do i need public ip in my local server iis to host the application ?
No you don’t. When you install the agent, it connects to the DevOps instance. Thought your local server should be able to access Internet if you are using Az DevOps services.
You can refer this video for more explanation.
Common Questions Answered for Web App Deployment to IIS
th-cam.com/video/w9KNMCn-59A/w-d-xo.html
Please, can you share the code in this tutorial so that we can try replicate the same thing you have done.
Here it is. I have added it now to description as well.
www.buymeacoffee.com/omegacodex/e/239549
@@omegacodex, Sorry, the link to the source code went to the buy coffee website. Or do we have to buy coffee before we can get it?
@@ogahgodwin2390 yes, its on buymeacoffee but its free download
I get the following error in "Download artifact" step - 2024-02-05T10:44:36.0522456Z ##[error]Failed in getBuildApi with error: Error: unable to verify the first certificate
2024-02-05T10:44:36.1275105Z ##[error]Error: unable to verify the first certificate
It could be an issue with the build pipeline. Make sure you are using the correct task for publishing artifacts. Use Publish pipeline artifact instead of publish build artifacts