I am currently finishing up creating a CI dev pipeline and referencing the following documentations
- https://www.andreasnesheim.no/using-vsts-and-github-to-set-up-cicd-for-your-node-js-grunt-application/
- https://www.c-sharpcorner.com/blogs/creating-cicd-pipeline-for-angular-and-hosting-in-azure-app-service
- https://azuredevopslabs.com/labs/vsts/nodejs/
- https://morioh.com/p/0d80bfd8ea27
The references all show that the artifacts get zipped up first, published, then deployed.
However, the project developer told me that after the .NET build, he just copies/deploys the generated AngularOutput artifacts to the Azure app service.
I tested it that way with archive task then publish, and the CI pipeline worked just fine. However, I also tested out publishing directly without prior archiving, and i changed the path to \Bundles\AngularOutput
, and the publish step succeeded just fine and displayed the published artifacts
So the question is, if publish works without zipping/archiving first, then can I directly deploy after the artifacts are published? and if so, what needs to be specified for the Azure App Service Deploy task: Package/Folder
?
If archiving task is necessary/recommended, thats fine, but does that means Azure App Service deploy will automatically extract the zipped up artifact?