Mohamed - this is amazing. I have moved from classic pipelines recently to yaml ones and this has opened my eyes. Extremely helpful.
@MRadwanMSF4 жыл бұрын
Thanks Naadir!
@amjadmahmood51072 ай бұрын
Brilliant Video Radwan. Informative and easy to follow.
@csmithDevCove4 жыл бұрын
Like this video - I would like to see how One triggers releases into multiple environmnets. I struggle with deployment strategy. Also - powershell core will work on both linux and windows. just need "get-childitem" command and you can get everything in current directory.
@TechTalkWithMuke3 жыл бұрын
Its really a great tutorial to get started with yaml based pipelines. Will be helpful while moving .ps1 based script into yaml.
@MRadwanMSF3 жыл бұрын
Glad it was helpful! Thank you!
@TechTalkWithMuke3 жыл бұрын
@@MRadwanMSF Can u please help me.. How can I write a pipeline in which I need to publish web app and webjobs on one app service for two dotnet core based projects which are in one solution.
@TechTalkWithMuke3 жыл бұрын
I have tried to create two different zip for each project in which webjob project path is DesktopBuildPackageLocation="$(build.artifactStagingDirectory)\App_Data\jobs\continuous\somethingApp.zip" but nothing is getting added into it
@Anubis101102 жыл бұрын
Thanks Mohamed, very informative and straight to the point.
@galilioXX4 жыл бұрын
Thanks Mohamed for this great tutorial!
@MRadwanMSF4 жыл бұрын
Glad it was helpful!
@stevenrichardson78764 жыл бұрын
Great video Mohamed, nice work
@MRadwanMSF4 жыл бұрын
Thanks Steven for your comment! I ham happy you like it!
@jonathasamaralbarbosa31364 жыл бұрын
Just a tip, using "ls -R" in bash will do the same as "dir /s /b" in windows
@MRadwanMSF4 жыл бұрын
Thanks!
@smusunuri4 жыл бұрын
Thanks Mohamed. You are amazing !!
@MRadwanMSF4 жыл бұрын
Thank you too!
@kenji31104 жыл бұрын
I'm usually using the classic view for developing the pipelines. But now I'd say it looks more clean when working with yaml files directly than classic (but this is more of a preference I guess). Using a yaml means you can track changes easier if you keep them in a repository.
@joonbyun1543 жыл бұрын
Thanks a lot for this great tutorial on Azure yaml pipeline. Wonder if I can have access to the YAML code you built during the video.
@MRadwanMSF3 жыл бұрын
Thanks! Yes, you can, it's open source using demo generator I used in the video
@HeyMani924 жыл бұрын
@ Mohamed Radwan - DevOps I'm your Facebook friend. and you made an awesome video.
@MRadwanMSF4 жыл бұрын
Happy you like it! Thanks for your comment
@tagoreanand25983 жыл бұрын
It's Amazing - What to know the process of exact YAML script that we can run a job without Artifact
@maidamsanthosh96124 жыл бұрын
Hi Mohamed, thanks for the video, exactly what I am looking for.. Can you please make a video on create multiple environments and deploy to them using yaml?
@MRadwanMSF4 жыл бұрын
I am happy it was useful...I will..... Thanks for your comment!
@maidamsanthosh96124 жыл бұрын
@@MRadwanMSF Thanks for the reply..
@Shinee3e3 жыл бұрын
Thank you so much Rawan
@MRadwanMSF3 жыл бұрын
You're welcome 😊
@xsoumendu3 жыл бұрын
Can you please explain what is the explanation of having '@2' .. '@1' .. '@4' in the task names? Like "VSBuild@1" or "NugetCommand@2".
@hank8usa4 жыл бұрын
It is a wonderful class demoed on internet. It looks like you are focusing more on YAML file, any video to example PS1 and SSH tasks on Linux servers as target of deployment? thanks a lot.
@MRadwanMSF4 жыл бұрын
Happy you like it! Thanks for your comment Not yet, keep connected, I may do it soon
4 жыл бұрын
Great video. Which tool do you recommend to create the diagrams? Min 05, Sec 20
@MRadwanMSF4 жыл бұрын
Thanks, happy you like it. I use PowerPoint to do that.
@AkashRajB4U2 жыл бұрын
Thanks for sharing your knowledge, i am facing one issue while downloading the the artifact from source file, below is the job. it says [error]Build type 'D:\tools\agent\_work\181\s\dist' is not recognized. - task: DownloadPipelineArtifact@2 displayName: Download Build Artifact (EAR) inputs: source: $(Pipeline.Workspace)\s\dist artifact: "reps" pipeline: 20 path: $(Build.ArtifactStagingDirectory)
@journeyofmars50182 жыл бұрын
in my class release pipeline, I have two stages: TEST and PROD which will deployed to different environment. the values for TEST and PROD are different, and TEST deployed automatically and PROD can only be deployed manually on release schedule. how do we handle that in YAML pipeline?
@rajivdixit21042 жыл бұрын
Hi @Radwan How would I decide which VM image would be require... like you have selected Window server 2016 with VS 2017 not Window server 2019 with VS 2019.... similarly I have a Python package for that, which Image should select Please suggest
@rambevara57023 жыл бұрын
Outstanding sir..please make the video on same with environments section.if already have , kindly share the link
@ramcmishra67272 жыл бұрын
Goood Vidio!
@seeacharya4 жыл бұрын
It is recommended that we use "publishPiplineArtifacts" now instead of 'publishBuildArtifacts' right now
@MRadwanMSF4 жыл бұрын
Great to know, thanks for your comment and sharing that!
@joejoe5704 жыл бұрын
Adding mutiple stages in one yaml requires us to copy paste or have duplicate tasks. Can we have a yaml file with one stage and reuse it for all environment?
@MRadwanMSF4 жыл бұрын
Excellent question! Yes, this is the YAML template, see the following link for more info: docs.microsoft.com/en-us/azure/devops/pipelines/process/templates?view=azure-devops
@shibadattmishra85974 жыл бұрын
Hi, I am going thru a multi stage deployment(Dev-PPE-Prod) in CD pipeline where i have 1 web.config & 1 xyz.js file needs to be excluded from the deployment process. i know there is something called "Additional Arguments" under IIS Web App Deploy task in CD phase but not sure how to do this. Would appreciate your help on this
@woutervanvegchel44724 жыл бұрын
Thanks Mohamed!
@MRadwanMSF4 жыл бұрын
No problem Wouter and thanks for your comment!
@woutervanvegchel44724 жыл бұрын
@@MRadwanMSF Hi Mohamed, is there another way of testing YAML pipelines then just running the pipeline?
@MRadwanMSF4 жыл бұрын
I found the syntax highlighted in the pipeline editor is not so bad but Unfortunately no other way
@yousefqasrawi6604 жыл бұрын
Great job, but please record this series in Arabic because we don't have enough information about devops field recorded in Arabic
@MRadwanMSF4 жыл бұрын
Sure, I had some videos in Arabic here kzbin.info/door/XL45yrrzvu3la8S9PM5Aug
@armandojorgelopezespinoza4762 жыл бұрын
I rename name of server and database, but when change webconfig to this name doesn't work. Furthermore min 25:27 name of webconfig database es ParstUnlimitedWebsite but name in azure is only PartsUnlimited. And supose that localserver not changed. Rigth ? Help?
@subhankarpati82264 жыл бұрын
I want to have the CI part in build pipeline and CD part in release pipeline using yaml..can you help me with the same?
@krupakarreddy82354 жыл бұрын
Please make a video of best branching strategy we can follow in azure devops
@MRadwanMSF4 жыл бұрын
Branch and merge is based on the project release and testing cycle so, you can do any one. See this video for Git tutorial kzbin.info/www/bejne/kJimdKGsbrGrsKM
@aakashcinecreations86674 жыл бұрын
Thanks a lot for detailed explanation but when following this method css,img,fonts and other few files are missing during build, when i change drop location to $(build.SourcesDirectory) no files are missing but getting error ##[error]Error: No package found with specified pattern: D:\a\1\a\drop\*.zipCheck if the package mentioned in the task is published as an artifact in the build or a previous stage and downloaded in the current job.
@aakashcinecreations86674 жыл бұрын
i have not changed anything on pipeline apart $(build.SourcesDirectory), downloading artifacts fine but when fetching getting error
@kashifaliuk4 жыл бұрын
Asak Radwan, I am struggling with indenting two tabs..not able to get rid of red underline error..please assist
@MRadwanMSF4 жыл бұрын
It's a tricky part, you just need to try it until you get it, never stop trying :)