No video :(

Multi-Stage CI/CD Pipelines as Code with YAML For Azure DevOps

Подписаться 19 тыс.

Просмотров 56 тыс.

50% 1

This video will focus on how to use CI/CD Pipelines as Code with YAML for Azure Pipelines. How to create a Multi-stage pipeline using YAML file. It will provide Pipelines as Code with YAML tutorial for Beginners | Multi-stage Azure Pipelines training.
Learn a complete tutorial for creating the Continuous Integration and Continuous Deployment pipelines as Code using YAML configuration Language.
This will cover, creating the application infrastructure on the cloud with Azure SQL, Azure Service Plan, Azure SQL Server and configure firewall rule to allow Azure Web App to communicate with Azure SQL Server.
Also, how to create a new YAML pipeline from Azure DevOps pipelines template for ASP.NET which include tasks in YAML that restore all the NuGet packages, build the ASP.NET application and running unit test, create Web.Zip of the app and store that on Azure Artifacts then pick this package and deploy it to the Web App and SQL Server on Azure.
Using YAML (Yet Another Markup Language). This allows us to access pipeline features as but with a markup file that can be managed like any other source control file. YAML build definitions can be added to a project by simply adding their source file to the root of the repository. Azure DevOps also provides default templates for popular project types, as well as a YAML designer to simplify the process of defining build and release tasks.
About the Author
-----------------------------
Video:
• Mohamed Radwan is a Pr...
Blog:
mohamedradwan.com
Linked-in
/ mohamedahmedradwan
GitHub
github.com/Dev...
Twitter:
/ mradwan06
Multi-stage #Azure #Azure_Pipelines_tutorial #Azure_training #Azure_DevOps #YAML
Links in the video
tldp.org/HOWTO/...
docs.microsoft...

Опубликовано:

29 авг 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 67

@amjadmahmood5107 21 день назад

Brilliant Video Radwan. Informative and easy to follow.

@NaadirAkhtar 4 года назад

Mohamed - this is amazing. I have moved from classic pipelines recently to yaml ones and this has opened my eyes. Extremely helpful.

@MRadwanMSF 4 года назад

Thanks Naadir!

@galilioXX 4 года назад

Thanks Mohamed for this great tutorial!

@MRadwanMSF 4 года назад

Glad it was helpful!

@Anubis10110 2 года назад

Thanks Mohamed, very informative and straight to the point.

@TechTalkWithMuke 3 года назад

Its really a great tutorial to get started with yaml based pipelines. Will be helpful while moving .ps1 based script into yaml.

@MRadwanMSF 3 года назад

Glad it was helpful! Thank you!

@TechTalkWithMuke 3 года назад

@@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.

@TechTalkWithMuke 3 года назад

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

@csmithDevCove 4 года назад

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.

@smusunuri 4 года назад

Thanks Mohamed. You are amazing !!

@MRadwanMSF 4 года назад

Thank you too!

@stevenrichardson7876 4 года назад

Great video Mohamed, nice work

@MRadwanMSF 4 года назад

Thanks Steven for your comment! I ham happy you like it!

@jonathasamaralbarbosa3136 4 года назад

Just a tip, using "ls -R" in bash will do the same as "dir /s /b" in windows

@MRadwanMSF 4 года назад

Thanks!

@seeacharya 4 года назад

It is recommended that we use "publishPiplineArtifacts" now instead of 'publishBuildArtifacts' right now

@MRadwanMSF 4 года назад

Great to know, thanks for your comment and sharing that!

@kenji3110 4 года назад

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.

@HeyMani92 4 года назад

@ Mohamed Radwan - DevOps I'm your Facebook friend. and you made an awesome video.

@MRadwanMSF 4 года назад

Happy you like it! Thanks for your comment

@Shinee3e 3 года назад

Thank you so much Rawan

@MRadwanMSF 2 года назад

You're welcome 😊

@joonbyun154 3 года назад

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.

@MRadwanMSF 3 года назад

Thanks! Yes, you can, it's open source using demo generator I used in the video

@tagoreanand2598 3 года назад

It's Amazing - What to know the process of exact YAML script that we can run a job without Artifact

@maidamsanthosh9612 4 года назад

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?

@MRadwanMSF 4 года назад

I am happy it was useful...I will..... Thanks for your comment!

@maidamsanthosh9612 4 года назад

@@MRadwanMSF Thanks for the reply..

@rambevara5702 2 года назад

Outstanding sir..please make the video on same with environments section.if already have , kindly share the link

@xsoumendu 3 года назад

Can you please explain what is the explanation of having '@2' .. '@1' .. '@4' in the task names? Like "VSBuild@1" or "NugetCommand@2".

@hank8usa 4 года назад

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.

@MRadwanMSF 4 года назад

Happy you like it! Thanks for your comment Not yet, keep connected, I may do it soon

@ramcmishra6727 Год назад

Goood Vidio!

@woutervanvegchel4472 4 года назад

Thanks Mohamed!

@MRadwanMSF 4 года назад

No problem Wouter and thanks for your comment!

@woutervanvegchel4472 4 года назад

@@MRadwanMSF Hi Mohamed, is there another way of testing YAML pipelines then just running the pipeline?

@MRadwanMSF 4 года назад

I found the syntax highlighted in the pipeline editor is not so bad but Unfortunately no other way

@AkashRajB4U 2 года назад

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)

@journeyofmars5018 Год назад

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?

3 года назад

Great video. Which tool do you recommend to create the diagrams? Min 05, Sec 20

@MRadwanMSF 3 года назад

Thanks, happy you like it. I use PowerPoint to do that.

@armandojorgelopezespinoza476 2 года назад

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?

@rajivdixit2104 2 года назад

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

@shibadattmishra8597 4 года назад

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

@yousefqasrawi660 4 года назад

Great job, but please record this series in Arabic because we don't have enough information about devops field recorded in Arabic

@MRadwanMSF 4 года назад

Sure, I had some videos in Arabic here ru-vid.com/show-UCXL45yrrzvu3la8S9PM5Aug

@joejoe570 3 года назад

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?

@MRadwanMSF 3 года назад

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

@subhankarpati8226 4 года назад

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?

@krupakarreddy8235 3 года назад

Please make a video of best branching strategy we can follow in azure devops

@MRadwanMSF 3 года назад

Branch and merge is based on the project release and testing cycle so, you can do any one. See this video for Git tutorial ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ZgCCnv9LxzA.html

@aakashcinecreations8667 4 года назад

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.

@aakashcinecreations8667 4 года назад

i have not changed anything on pipeline apart $(build.SourcesDirectory), downloading artifacts fine but when fetching getting error