Concise, clear and great explanation. Only following this tutorial, I managed to deploy my application without opening stack overflow or other forum sites. This is my first deployment using azure.
This guy rocks! Even going through the Microsoft blog post on this and multiple vids left me in the dark but now I can see the issue was with where the build file is and how to go about pointing to it. Lifesaver buddy. Thanks!
Thanks, this video was very helpful, everything worked first time for me on a project I made using create-react-app, but then I made another that used Vite instead. Everything was the same except I got an error that the publish artifact: drop step couldn't find the path to publish "build", after a while i realized Vite doesn't name the build folder "build" it names it "dist". So on the Publish Artifact: Drop > Path to Publish > i entered "dist" instead and it worked
This is a great video! I followed every step, the drop was created and in the Development Center I see a message "Deployed Successfully to production", but for some reason is not updating production. Any ideas?
If the Drop folder is having the proper build files, the issue must be with the deployment part or App settings. As a first step, you can check it out the deployed folder in Azure Web App has the right files. For that you can use the Admin tool Kudu. This tool will allow you to see the folder structure where you deployed in Azure. You can refer this Video to understand how to connect and see the folder structure using Kudu or FileZilla. th-cam.com/video/3wF99gvBFcw/w-d-xo.html . If the deployed folder has all the files, then the issue must be with your Web app setup Or can be because of some extra folders added in the deployed location (This can be because of your folder structure you are using in the source code). In that case you have to either remove that folder in the Drop folder or access the website with the extra folder in the URL. Let me know if this resolved your issues. Else we will dig into details..
Thanks for sharing.. While building react pipeline, I am getting this warning ##[warning]Directory '/home/vsts/work/1/a' is empty. Nothing will be added to build artifact 'drop'. This causing my release pipeline to fail.
This must be because of the folder structure difference in your project. Where exactly your project.json file present? Open your Azure Repository and check your folder structure and see if it is different at the 2:20 minutes in this video? If your package.json folder is inside any folder (which is different from this video), go to the video 3:27 minutes where you are setting up the "npm install" job and select the 3 dots after the "working folder that contains the package.json" and choose the right folder where your package.json file present. Same action required for "npm build" job as well. If you are still getting this error you can send me the screenshots to my mail id "techiesloungeteam@gmail.com" and I am happy to help you. Please message if this issue resolved.
Thanks for this. However when I successfully deployed my react app on Azure App service via Azure DevOps, I get the error "The service is unavailable" on a white screen upon accessing the Azure URL. Kindly advise. thanks
Can you do a video on next js deployment on Azure with a local agent as MS doesn't provide free parallism. I'm getting an internal error after following all the steps.
Great video. Got me a lot further than other instructions, but I have an issue I just can't get past. Just as the video has at 5:05, I have the build artifacts 'drop' folder containing files (but not a zip file). It's at 10:02, with the release, where things differ. In my log, the next line after "Got service connection details for Azure App Service:'testmyreact'", I get the line "Package deployment using ZIP Deploy initiated." I don't have the references to WEBSITE_RUN_FROM..... And it definitely doesn't go to "Successfully deployed web package to App Service". Instead it has "Preparing deployment...", references to oryx build, and eventually "Detecting platforms...", "Could not detect any platform in the source directory.", "Error: Couldn't detect a version for the platform 'nodejs' in the repo.". A few other errors that eventually leads to "##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details". I've been researching this for a few days without luck. I'm guessing I'm missing something simple. Any ideas out there?
Is it possible to change the config from let´s say if I use Maven but I suppose to use React instead. Is that possible or do I need to create a total new project and do everything from the beginning again?
Appreciate the video !! I have been trying to deploy nextjs app to Azure DevOps and experiencing challenges at the time of publishing artifacts. While adding The Publish Artifact to the pipeline , I entered build under under Path to Publish and got the error "Publishing build artifacts failed with an error: Not found PathtoPublish: D:\a\1\s\build" I also replaced build with next and got the same error Can you please suggest what needs to be entered under "Path to publish"? Any help would be appreciated
Hi Vivek Murli, issue is because your "Publish build artifacts" task (3rd Task) is not able to locate the "build" folder. This must be because, your package.json may not be on the root folder ! Suppose your package.json file is under a different folder eg. "Sample/package.json", you have to do the following two steps : 1) In the Build pipeline, 2nd Task ie. "npm build" -> "Working folder that contains package.json" field you should mention "Sample" 2) in the Build pipeline, 3rd Task ie "Publish build artifacts" -> "Path to publish" field you can mention "Sample\build" This should resolve your problem. Let me know if the error still not resolved!
Hi @@ludovicbenard8679, issue is because your "Publish build artifacts" task (3rd Task) is not able to locate the "build" folder. This must be because, your package.json may not be on the root folder ! Suppose your package.json file is under a different folder eg. "Sample/package.json", you have to do the following two steps : 1) In the Build pipeline, 2nd Task ie. "npm build" -> "Working folder that contains package.json" field you should mention "Sample" 2) in the Build pipeline, 3rd Task ie "Publish build artifacts" -> "Path to publish" field you can mention "Sample\build" This should resolve your problem. Let me know if the error still not resolved!
hey, I've been getting a warning and immediately after that an error... the only message for the warning and error I get is "Couldn't find a debug log in the cache or working directory" I've been following your tutorial step by step but I got stuck in the pipelines... not that I have done anything wrong, but I think there's a setting required maybe? Does it have to do that I am doing this on a Mac computer?
This must be because of the folder structure difference in your project. Where exactly your project.json file present? Open your Azure Repository and check your folder structure and see if it is different at the 2:20 minutes in this video? If your package.json folder is inside any folder (which is different from this video), go to the video 3:27 minutes where you are setting up the "npm install" job and select the 3 dots after the "working folder that contains the package.json" and choose the right folder where your package.json file present. Same action required for "npm build" job as well. If you are still getting this error you can send me the screenshots to my mail id "techiesloungeteam@gmail.com" and I am happy to help you. Please message if this issue resolved.
@@TechiesLounge Thank you for how quickly you replied. You were right about the folder structure. Azure doesn't allow empty folders so what I did is I created the deployment folder myself and then added and empty file. After that I changed the directory address in the pipeline settings. The deployment process works fine now. However, I have a new issue. When I follow the url of my web app I get this "You do not have permission to view this directory or page." Any ideas how I can solve this issue? Thanks again for all your help!
@@Joelpyro because of the folder structure change, the website also might have added some additional folder in the URL. What you can do is, go to the Azure portal and open then the Kudu tool from the Web app and see where exactly the files are deployed. One on my another video I have mentioned how to deploy using Kudu admin tool. Seeing that you can understand how to see the folder structure once after you deployed using Azure DevOps. Please share me the screenshots to my mail id if the issue still persists. You can refer this URL th-cam.com/video/3wF99gvBFcw/w-d-xo.html To resolve the folder structure issue, you can make changes in the Publish Artifacts Task and remove the additIonal folder if it is adding.
@@TechiesLounge I finally found the problem. It seems that the building process goes through, but no files are created in the directory I pointed. When I look inside the "drop" folder, there's nothing there. So even though the building process is completed, the files are not in the "drop" folder, and I have no idea where they are.
@Techies Lounge I got a warning "Directory 'D:\a\1\a' is empty. Nothing will be added to build artifact 'drop'. but build pipeline got succeeded. Please suggest. Many thanks.
This must be because of the folder structure difference in your project. Where exactly your project.json file present? Open your Azure Repository and check your folder structure and see if it is different at the 2:20 minutes in this video? If your package.json folder is inside any folder (which is different from this video), go to the video 3:27 minutes where you are setting up the "npm install" job and select the 3 dots after the "working folder that contains the package.json" and choose the right folder where your package.json file present. Same action required for "npm build" job as well. If you are still getting this error you can send me the screenshots to my mail id "techiesloungeteam@gmail.com" and I am happy to help you. Please message if this issue resolved.
Runtime Stack: Select the platform or framework you used to create and run your web app. When we are deploying a React application , we just need a web server which renders the ReactJS code to the client side browser and browser executes the ReactJS code. So we can use any web server to deploy a FrontEnd applications.
@@TechiesLounge sorry, actually that was exactly why I asked that question, we created react app using NodeJS right?.. so the runtime stack should be NodeJS right? why asp.net??
Hi @@anandhu5082, We are not using NodeJS to create the ReactJS application, instead we are using NPM (Node Package Manager) to create the ReactJS application. But Once we create the release files using NPM RUN BUILD, there is no dependency with NPM as well and it will be a pure ReactJS application with HTMLs, Javascript and CSS.
Concise, clear and great explanation.
Only following this tutorial, I managed to deploy my application without opening stack overflow or other forum sites.
This is my first deployment using azure.
Glad it helped. Thanks for your support.
This guy rocks! Even going through the Microsoft blog post on this and multiple vids left me in the dark but now I can see the issue was with where the build file is and how to go about pointing to it. Lifesaver buddy. Thanks!
Glad I could help you.
That's what tripped me up as well 😂
Self-explanatory ! A perfect video for freshers in Azure Devops . Thank you!
Simple and precise tutorial. A perfect video for a beginner who wants to experience their first hands-on! Thank you so much!
Glad you enjoyed it!
Thanks, this video was very helpful, everything worked first time for me on a project I made using create-react-app, but then I made another that used Vite instead. Everything was the same except I got an error that the publish artifact: drop step couldn't find the path to publish "build", after a while i realized Vite doesn't name the build folder "build" it names it "dist". So on the Publish Artifact: Drop > Path to Publish > i entered "dist" instead and it worked
Nice story
You're a lifesaver
Best Tutorial Ever, Really straight forward and easy to follow. Much appreciated !
Glad you think so ! Really appreciate your support.
The is the best. Quick and precise.
He is an absolute great tutor
Glad you think so..
Good information for techies 👍
Thank you so much for this one. So easy to follow and no BS. Subscribed!
Great tutorial. Straight to point. Thanks
This is a great video! I followed every step, the drop was created and in the Development Center I see a message "Deployed Successfully to production", but for some reason is not updating production. Any ideas?
If the Drop folder is having the proper build files, the issue must be with the deployment part or App settings.
As a first step, you can check it out the deployed folder in Azure Web App has the right files. For that you can use the Admin tool Kudu. This tool will allow you to see the folder structure where you deployed in Azure. You can refer this Video to understand how to connect and see the folder structure using Kudu or FileZilla. th-cam.com/video/3wF99gvBFcw/w-d-xo.html .
If the deployed folder has all the files, then the issue must be with your Web app setup Or can be because of some extra folders added in the deployed location (This can be because of your folder structure you are using in the source code). In that case you have to either remove that folder in the Drop folder or access the website with the extra folder in the URL.
Let me know if this resolved your issues. Else we will dig into details..
Thanks for sharing.. While building react pipeline, I am getting this warning ##[warning]Directory '/home/vsts/work/1/a' is empty. Nothing will be added to build artifact 'drop'. This causing my release pipeline to fail.
This must be because of the folder structure difference in your project. Where exactly your project.json file present? Open your Azure Repository and check your folder structure and see if it is different at the 2:20 minutes in this video? If your package.json folder is inside any folder (which is different from this video), go to the video 3:27 minutes where you are setting up the "npm install" job and select the 3 dots after the "working folder that contains the package.json" and choose the right folder where your package.json file present. Same action required for "npm build" job as well.
If you are still getting this error you can send me the screenshots to my mail id "techiesloungeteam@gmail.com" and I am happy to help you. Please message if this issue resolved.
Thank you very much. Your tutorial saved my day
Good presentation..👍
Thank you 🙂
Thank you for such a great video, are you planning to make any video on ASP.NET core as backend API and React as a frontend to deploy on the server?
Sure
Is it possible to trigger the aab and ipa files using the Titanium application. I don't see an option for custom apps.
🎉🎉 you are really super ,Thank you
Thanks for this.
However when I successfully deployed my react app on Azure App service via Azure DevOps, I get the error "The service is unavailable" on a white screen upon accessing the Azure URL. Kindly advise. thanks
Can you do a video on next js deployment on Azure with a local agent as MS doesn't provide free parallism. I'm getting an internal error after following all the steps.
Hi, Also wondering how we can pass enviroment variables using this step.
You are the best. Thank you!
Glad you think so !!
Great video. Got me a lot further than other instructions, but I have an issue I just can't get past.
Just as the video has at 5:05, I have the build artifacts 'drop' folder containing files (but not a zip file).
It's at 10:02, with the release, where things differ.
In my log, the next line after "Got service connection details for Azure App Service:'testmyreact'", I get the line "Package deployment using ZIP Deploy initiated." I don't have the references to WEBSITE_RUN_FROM..... And it definitely doesn't go to "Successfully deployed web package to App Service".
Instead it has "Preparing deployment...", references to oryx build, and eventually "Detecting platforms...", "Could not detect any platform in the source directory.", "Error: Couldn't detect a version for the platform 'nodejs' in the repo.". A few other errors that eventually leads to "##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details".
I've been researching this for a few days without luck. I'm guessing I'm missing something simple.
Any ideas out there?
what about react-router-dom? If I have a few routes do I need to make additional steps?
you need to add web.config file in your public folder checkout stack overflow someone has posted the answer what to write in that file
Is it possible to change the config from let´s say if I use Maven but I suppose to use React instead.
Is that possible or do I need to create a total new project and do everything from the beginning again?
Appreciate the video !!
I have been trying to deploy nextjs app to Azure DevOps and experiencing challenges at the time of publishing artifacts.
While adding The Publish Artifact to the pipeline , I entered build under under Path to Publish and got the error "Publishing build artifacts failed with an error: Not found PathtoPublish: D:\a\1\s\build"
I also replaced build with next and got the same error
Can you please suggest what needs to be entered under "Path to publish"?
Any help would be appreciated
I have the same error
@@ludovicbenard8679 I managed to fix it with the help of the article
parveensingh.com/next-js-deployment-on-azure-app-service/
Hi Vivek Murli, issue is because your "Publish build artifacts" task (3rd Task) is not able to locate the "build" folder. This must be because, your package.json may not be on the root folder !
Suppose your package.json file is under a different folder eg. "Sample/package.json", you have to do the following two steps :
1) In the Build pipeline, 2nd Task ie. "npm build" -> "Working folder that contains package.json" field you should mention "Sample"
2) in the Build pipeline, 3rd Task ie "Publish build artifacts" -> "Path to publish" field you can mention "Sample\build"
This should resolve your problem. Let me know if the error still not resolved!
Hi @@ludovicbenard8679, issue is because your "Publish build artifacts" task (3rd Task) is not able to locate the "build" folder. This must be because, your package.json may not be on the root folder !
Suppose your package.json file is under a different folder eg. "Sample/package.json", you have to do the following two steps :
1) In the Build pipeline, 2nd Task ie. "npm build" -> "Working folder that contains package.json" field you should mention "Sample"
2) in the Build pipeline, 3rd Task ie "Publish build artifacts" -> "Path to publish" field you can mention "Sample\build"
This should resolve your problem. Let me know if the error still not resolved!
very very helpful, you saved my day. Thanks great work
Glad it helped!
Very Cool! Greay tutorial! Thank you! 🙏
This is done the right way. Thanks man!
please create video on Build once Deploy Many with ReactJs and Azure with different environment
hey, I've been getting a warning and immediately after that an error... the only message for the warning and error I get is "Couldn't find a debug log in the cache or working directory" I've been following your tutorial step by step but I got stuck in the pipelines... not that I have done anything wrong, but I think there's a setting required maybe? Does it have to do that I am doing this on a Mac computer?
This must be because of the folder structure difference in your project. Where exactly your project.json file present? Open your Azure Repository and check your folder structure and see if it is different at the 2:20 minutes in this video? If your package.json folder is inside any folder (which is different from this video), go to the video 3:27 minutes where you are setting up the "npm install" job and select the 3 dots after the "working folder that contains the package.json" and choose the right folder where your package.json file present. Same action required for "npm build" job as well.
If you are still getting this error you can send me the screenshots to my mail id "techiesloungeteam@gmail.com" and I am happy to help you. Please message if this issue resolved.
@@TechiesLounge Thank you for how quickly you replied. You were right about the folder structure. Azure doesn't allow empty folders so what I did is I created the deployment folder myself and then added and empty file. After that I changed the directory address in the pipeline settings. The deployment process works fine now. However, I have a new issue. When I follow the url of my web app I get this "You do not have permission to view this directory or page." Any ideas how I can solve this issue? Thanks again for all your help!
@@Joelpyro because of the folder structure change, the website also might have added some additional folder in the URL. What you can do is, go to the Azure portal and open then the Kudu tool from the Web app and see where exactly the files are deployed. One on my another video I have mentioned how to deploy using Kudu admin tool. Seeing that you can understand how to see the folder structure once after you deployed using Azure DevOps. Please share me the screenshots to my mail id if the issue still persists. You can refer this URL th-cam.com/video/3wF99gvBFcw/w-d-xo.html
To resolve the folder structure issue, you can make changes in the Publish Artifacts Task and remove the additIonal folder if it is adding.
@@TechiesLounge I finally found the problem. It seems that the building process goes through, but no files are created in the directory I pointed. When I look inside the "drop" folder, there's nothing there. So even though the building process is completed, the files are not in the "drop" folder, and I have no idea where they are.
Hi, thanks for the video. Is it the same process with a GRANDstack app ? (GrapQL, React, Apollo, Neo4j Database)
Yes. But the Pipeline Tasks you choose to install and build may be different for other project types like GrapQL, .NET etc.
That was clean and neat explanation.
i did the same thing and i am still seeing the default page when i browse to the azurewebsite
sorry sir ! where can I put variable in .env?
@Techies Lounge I got a warning "Directory 'D:\a\1\a' is empty. Nothing will be added to build artifact 'drop'. but build pipeline got succeeded. Please suggest. Many thanks.
This must be because of the folder structure difference in your project. Where exactly your project.json file present? Open your Azure Repository and check your folder structure and see if it is different at the 2:20 minutes in this video? If your package.json folder is inside any folder (which is different from this video), go to the video 3:27 minutes where you are setting up the "npm install" job and select the 3 dots after the "working folder that contains the package.json" and choose the right folder where your package.json file present. Same action required for "npm build" job as well.
If you are still getting this error you can send me the screenshots to my mail id "techiesloungeteam@gmail.com" and I am happy to help you. Please message if this issue resolved.
Thank you very much.
Glad you enjoyed it ! Really appreciate your support.
Does this work for next js?
extremely useful!!! thanks for sharing. what if i want to add a second member to deploy form his computer?
i want to deploy to the same app from another account
you saved my life man!!!!!
Glad it helped!
Excelente
why do we select Runtime stack ASP.NET? instead of Node JS @6:30
Runtime Stack: Select the platform or framework you used to create and run your web app.
When we are deploying a React application , we just need a web server which renders the ReactJS code to the client side browser and browser executes the ReactJS code. So we can use any web server to deploy a FrontEnd applications.
@@TechiesLounge sorry, actually that was exactly why I asked that question, we created react app using NodeJS right?.. so the runtime stack should be NodeJS right? why asp.net??
Hi @@anandhu5082, We are not using NodeJS to create the ReactJS application, instead we are using NPM (Node Package Manager) to create the ReactJS application. But Once we create the release files using NPM RUN BUILD, there is no dependency with NPM as well and it will be a pure ReactJS application with HTMLs, Javascript and CSS.
@@TechiesLounge perfect thankyou!.
Good one 👍
beautiful
Not a git repository (or any of the parent directories): .git how to resolve this
Good video
Thanks
Everything up-to-date Branch 'master' set up to track remote branch 'master' from 'origin'. But your project is emty
This should be the default Azure documentation
Getting below error, How to fix ?
32 error code EBADPLATFORM
33 error notsup Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
34 error notsup Valid OS: darwin
34 error notsup Valid Arch: any
34 error notsup Actual OS: win32
34 error notsup Actual Arch: x64
Don't think it is simple. But nice tutorial!
It is simple.. watch two more times and everything will be clear for you !
my react build now needs to say, "run-script build " be aware.
Thank you ❤️