Dear Appveyor Support,
I am working on deploying an ASP.NET app to IIS. When the build succeeds, I deploy it but encounter an error as shown in the picture below. It seems that the deployment configuration in my file is not being read, causing the site_name to be null.
Could you please let me know what I might be missing?

#1 Posted by Feodor Fitsner Support staff on 19 Sep, 2024 06:20 PM
Can you drop a link to the build being deployed and the deployment itself?
#2 Posted by Nguyen Viet Hie... on 20 Sep, 2024 02:15 AM
Hi Mr. Feodor,
I'm new to this, and I'm not exactly sure which link you need, but here is the link to my build:
https://ci.appveyor.com/project/TopasFerryOps/topasferryopsnwt/builds/50614376
And here is the link to my deployment:
https://ci.appveyor.com/project/TopasFerryOps/topasferryopsnwt/deployment/4335105/job/em0s1ctiv6y4v4g4
Is this what you're looking for?
In the Environment, if I set the default site_name like in the picture below, it works, but I want to retrieve it from the deploy file instead
#3 Posted by Feodor Fitsner Support staff on 20 Sep, 2024 05:57 PM
So, that build https://ci.appveyor.com/project/TopasFerryOps/topasferryopsnwt/buil... didn't kick off the deployment because it's a PR build and deployments are disabled in PR builds. You can see in the the build log - it uploads the artifact but deployment is not happening. I can also confirm build configuration has environment deployment configured with additional settings. I believe you did manual deployment on Environments page - this case variables from the build won't be passed.
However, you can enable deployments in PR builds on General tab of project settings in AppVeyor ("Enable deployments in Pull Requests" option). Once enabled the deployment will be started during the build and custom variables will be passed to an agent. Let me know.
#4 Posted by Nguyen Viet Hie... on 24 Sep, 2024 06:47 AM
Yes, you're right. Now I know what the problem is. Thanks for the information