Exactly..I was expecting someone to show me how to set the steps to set up a deployment pipeline in DevOps to deploy a Logic App to Azure Portal. I got to 6:37 and realized this ain't it. I'll never get the last six minutes of my day back. What a gyp
I wanna start of by saying great video! Could you expand upon the creation of the release pipeline as you say in the title? It would be nice to see you build the pipeline from scratch. Walk us through stuff like what's an "artifact" and how do you use it in this particular situation? It would also be nice if you would elaborate on what a "job" is and how to use it in regards to deploying a logic app. I really like your thoroughness, but this is more of a demonstration of something already setup instead of an actual step-by-step guide on how to build a release pipeline.
Thank you for the great video!!! Please share topics related to deploying onpremise 2016/2019 custom solution using Azure DevOps pipeline! Thank you in advance!
I would appreciate if you could explain how to create a ci cd pipeline for logic apps. And also. Multiple logic app deployment from one solution. I have 15 integration means 15 logic apps creation. I am thinking of adding the proeject in same solution but how should I deploy it to get created in portal ..
Hi Giuliano, I am also confused on how to deploy the connectors used by logic apps to different environments. When I tried to look at the connections I am unable to find how it's connected like oauth etc. Can you please comment on the solution if you already came across
Hi Phani, If you open the logic app on Azure you'll find "Logic App Code View" clicking there you'll be able to see in the code, connections with URLs and subscriptions
It is just the release pipeline with one task inside, Azure resource group Deployment, where you have to add your Azure subscribe that you want to target, the template json and the parameter json in template parameters field, incremental deployment mode and that's it
![BOWKYLION - วิงวอน (ex-change) [Official MV]](http://i.ytimg.com/vi/cLdnZWDaO-w/mqdefault.jpg)
The title fooled me into thinking this video was explaining how to setup a CI/CD pipeline, not just executing it.
+1
Exactly..I was expecting someone to show me how to set the steps to set up a deployment pipeline in DevOps to deploy a Logic App to Azure Portal. I got to 6:37 and realized this ain't it.
I'll never get the last six minutes of my day back. What a gyp
I wanna start of by saying great video!
Could you expand upon the creation of the release pipeline as you say in the title? It would be nice to see you build the pipeline from scratch. Walk us through stuff like what's an "artifact" and how do you use it in this particular situation? It would also be nice if you would elaborate on what a "job" is and how to use it in regards to deploying a logic app.
I really like your thoroughness, but this is more of a demonstration of something already setup instead of an actual step-by-step guide on how to build a release pipeline.
Hi Anders, I appreciate your feedback and I added it to my to do list, I'll release a new video
Thank you for the great video!!! Please share topics related to deploying onpremise 2016/2019 custom solution using Azure DevOps pipeline! Thank you in advance!
I would appreciate if you could explain how to create a ci cd pipeline for logic apps. And also. Multiple logic app deployment from one solution. I have 15 integration means 15 logic apps creation. I am thinking of adding the proeject in same solution but how should I deploy it to get created in portal ..
Thanks but where's the building the pipeline for logic app part bro? It's totally missing in the video 🤔
Hi,
Thanks for watching.
You can refer to my blog post
delucagiuliano.com/building-a-release-pipeline-on-azure-devops-for-logic-apps
@@DeLucaGiulian Even your blog does not explain how to setup. The title is misleading
Hi Giuliano De Luca,
Does the URL for http trigger changed after deployment?
Hi,
Thank you for watching, if it's the first time that you deploy the logic app in a new azure environment the URL will change.
Hi Giuliano De Luca,
Is there a way to deploy without the url change
Hi Phani,
As far as I know this is not possible, when you create the Logic App in Azure the first time, Azure dinamically assign the URL
Hi Giuliano,
I am also confused on how to deploy the connectors used by logic apps to different environments.
When I tried to look at the connections I am unable to find how it's connected like oauth etc. Can you please comment on the solution if you already came across
Hi Phani,
If you open the logic app on Azure you'll find "Logic App Code View" clicking there you'll be able to see in the code, connections with URLs and subscriptions
how do you set up the pipeline? in the video you just show how to trigger it...
It is just the release pipeline with one task inside, Azure resource group Deployment, where you have to add your Azure subscribe that you want to target, the template json and the parameter json in template parameters field, incremental deployment mode and that's it
Misleading title... you aren't showing how to build a release pipeline.
sorry, but dark theme is aweful when watching on youtube/beamer. content seems to be interesting...use light theme and better screen resolution.
Thanks for your feedback I appreciate, that was my first video, you can check other videos which are definitely better
misleading title i would expect to show the steps to setup the pipelines