Finally one understandable Demo with nessesary explanations what the creation steps actually mean. And how a beginner can be enabled to start with all the overwhelming options. Please do more of this maybe in complex szenarios. (without copying and pasting Code). Thank you for your great work.
@snowke5095 Жыл бұрын
Wow, even with previous Azure DevOps experience, I picked up a surprisingly large amount of information in two hours. Kudos to presenting the information in such a clean and understandable format. Thank you!
@vasilypodguzov4442 жыл бұрын
Nana, you are the best woman in IT! Thank you! Absolutely amazing
@AzureDevOps2 жыл бұрын
She is awesome, it was an absolute pleasure to work with her
@bhogikorada54632 жыл бұрын
Absolutely..
@ntsikelelonelsonmbekwa3231 Жыл бұрын
thank you Nana and april, appreciate the effort you guys put into walking us through azure devops. would recommend this video to more beginners in azure devops
@haniyanunes8092 Жыл бұрын
Incredible offer 100% off on Exam Test for AWS Certified DevOps Engineer - Professional Mock Test for next 05 days. So Hurry up and avail this offer. This AWS practice quiz consists of 65 questions with a mix of questions on core AWS services, including all services which are at the AWS Certified DevOps Engineer - Professional level. Please note that, unlike the real AWS Certified DevOps Engineer - Professional, so you can take as much time as required to answer each question. At the end of the test, you get to review your answers and find detailed explanations of why each answer is wrong or right along with reference links for each question. This will help you identify your strength and weaknesses. With these popular Practice Tests, you’ll know when you are ready to pass your AWS Certified DevOps Engineer - Professional. URL: www.udemy.com/course/aws-certified-devops-engineer-professional-mock-test/?couponCode=AWSFREEMAY Coupon Code: AWSFREEMAY
@mohammadnabulsi1281 Жыл бұрын
You actually nailed the title of your video. From Zero to Hero. Very nicely explained from someone with zero knowledge of DevOps like me
@mohammadnabulsi1281 Жыл бұрын
I meant to someone not from someone 🤪
@AzureDevOps Жыл бұрын
Thank you Mohammed!
@zieyob10 ай бұрын
Clear, concise and informative breakdown. You guys are awesome!
@mechwarrior83 Жыл бұрын
What an amazing video and a breakdown! Learnt so so much from this, thank you both! Nana and April teaming up like when the Avengers first came together.
@AzureDevOps Жыл бұрын
Thank you! I love being compared to the Avengers!!
@amgdy Жыл бұрын
34:44 Retrospectives isn't part of the OOB Azure DevOps Organization and you have to install an extension to get it!
@AzureDevOps Жыл бұрын
Yes, but easy to install and configure.
@amgdy Жыл бұрын
@@AzureDevOps I know, I would preferred if that was mentioned in the video to demonstrate that feature and the extensibility feature of Azure DevOps by adding extensions.
@AzureDevOps Жыл бұрын
@@amgdy that's great feedback. Thank you!
@megastarling Жыл бұрын
1:54:18 DeployToProd should depends on Approve ("dependsOn" in second job). Now it is done in parallel and deployment does not wait for approval.
@nguyennhatquang6612 Жыл бұрын
Please help to confirm this
@AzureDevOps Жыл бұрын
@@nguyennhatquang6612 Thanks for catching that.
@brookster77722 жыл бұрын
Both April and Nana must be the best communicators and presenters of DevOps knowledge! I hope you two are planning to build your own company and do very well for yourselves! You deserve it. I will be recommending your videos to my teams when the time is right to teach somebody everything about DevOps ❤
@AzureDevOps2 жыл бұрын
Thank you ! We'll see what the future holds :)
@johannes.sbw-media11 ай бұрын
21:31 Net item in agile has no User story or bug
@bronstet9 ай бұрын
Thank you for this concise explanation, ladies.
@dibasbehera72 жыл бұрын
Informative tour on Azure DevOps. Love it! 🥰🥰
@rajkumararora7366 Жыл бұрын
Very well explained. Thank you for sharing your efforts!
@TheBeach5563 Жыл бұрын
Thank you both so much for sharing. A lot of people need this. i am just getting started with aZ-104 Azure administrator right now but this will be next.
@AzureDevOps Жыл бұрын
Best of luck!
@thomaslindh40802 жыл бұрын
Thank you Nana & April for such great session. ❤
@AzureDevOps2 жыл бұрын
Thank you Thomas!
@dannyhd8301 Жыл бұрын
Great content , when I exactly needed it . Thank you. , both .
@vsurend18 ай бұрын
Excellent session Nana, you have given great insight on Azure devops for beginners...
@brandonhunter3036 Жыл бұрын
This was pretty fantastic. Recently got thrust into ADO and got stuck on the Pipeline work. This helped me to think through some things better so thanks much.
@AzureDevOps Жыл бұрын
Glad it helped!
@commonman5768 Жыл бұрын
Thank you ma'am. This helps for all students. Thanks...❤
@ah_ay_ Жыл бұрын
Thanks a lot Nana and April for this very interesting video, I really appreciated it. Could you please update the readme with infra details ? thanks a lot
@ManishPanwar9 ай бұрын
This is the best crash course hands on❤
@miguelafz Жыл бұрын
Great job ! big overview :) thank you very much!I have some questions more... how synchronise azure steps with agile sprint ? (like : does a sprint include board to Artifcat and the tests are outside of the sprints ? ) What mean the item status CLOSED for devops ? and why we don't need to ensure on test plan every US is tested ?
@rainertelesko98942 жыл бұрын
Great tutorial. All features are nicely explained.
@AzureDevOps2 жыл бұрын
Thank you Rainer! Really glad you enjoyed the content!
@ijazm9 ай бұрын
Thanks so much for this wonderful video.
@avidshowgoer Жыл бұрын
Thanks a lot for such an insightful session!
@plartoo8 ай бұрын
How come the presenter is seeing Bug, Issue, Task, Test Case, User Story at @0:13:29 whereas I see only Epic, Issue and task under 'New Work Item'. Some things that she is showing here are different than what it looks for me in DevOps.
@georgezviadgoglodze7810 Жыл бұрын
Nana is awesome
@yoconugall1714 Жыл бұрын
You guys are superb!!👏👏👏👏
@AdamSysPL Жыл бұрын
Amazing video. Thanks 🙏
@oa3699 Жыл бұрын
Hi April & Nana, thanks very much for creating this video !! Pls, I am not able to open the website / link you suggested at the beginning of this video.. Are there any other options, pls ? Many thanks..
@AzureDevOps Жыл бұрын
Hi @oa3699 can you please confirm which link you're referring to?
@oa3699 Жыл бұрын
@@AzureDevOps I am referring to the link / web page where you specify your name, etc. Then you will be able to download the links.. The part I am referring to is at the beginning of your video, please..
@AzureDevOps Жыл бұрын
@@oa3699 use the link: aka.ms/techworldwithnana
@bharathsimha28222 жыл бұрын
Fabulous work you both are did...come to question, we are deploying Salesforce Environment we are used JFrog Artifactory but we are planning to move Azure artifact's is it fine approach..how to publish the artifact's..what is azure feed should I deploy old articats using artifacts..
@AzureDevOps2 жыл бұрын
Hello Bharath! Great question! JFrog Artifactory has an extension: www.jfrog.com/confluence/display/JFROG/Artifactory+Azure+DevOps+Extension. That's one thing to look at. Then depending on what type of artifacts you have you can absolutely migrate them over. I've used PowerShell in the past. Look at this post to help: learn.microsoft.com/azure/devops/artifacts/tutorials/migrate-packages?view=azure-devops&tabs=Windows
@bentaybiaHabib11 ай бұрын
Hi @bharathsimha2822, I need some help plz. I am a junior .Net fullsatck developer and I want to understand the relationship between branches and environments. Nana mentioned that when we want to deployDev, deployTest and deployProd, we should trigger the main branch. At my team, everyone works on his own branch then he make a Pull request on azure devops (a request to merge his own branch with the dev branch). At our project, we have three environments (dev, test and prod) and I want to understand what really happen after the feature branches were merged into the dev branch. There will be a merge from dev branch to test branch then to main branch ? Each environemnt will be deployed from each branch or all the environment will be deployed from only the main branch ? Thanks in advance.
@MicheleMassari Жыл бұрын
Thanks this video give me many informations I was looking for, I want to ask you if it's possible to run automated tests on pull request. We need to do some automatic checks on code before the PR go to approval by reviewers... Thanks
@AzureDevOps Жыл бұрын
Yes you can! Configure your Build Validation: Set a policy requiring changes in a pull request to build successfully with the protected branch before the pull request can be completed.
@Shahroz75 Жыл бұрын
Great session. Thanks
@peacefulminds36289 ай бұрын
Thanks for this video. Is there any prerequisite for this tutorial? I come from a non-IT background. No coding experience. Starting from scratch.
@rushikeshdeshmukh3852 жыл бұрын
you both are doing good work...I also want to learn azure devops but currently I am learning aws devops ...and some people said don't learn aws devops and azure devops simultaneously...you might get confuse at interview , is it right ? simultaneously learning aws and azure devops is appropriate or not ? what is your opinion on it ?
@tejasbachhav28312 жыл бұрын
Take one step at a time. Aws or azure. Learn any one first and then go with other
@AzureDevOps2 жыл бұрын
Learn one and become proficient. Azure DevOps deploys to all clouds and on-prem. It's an extremely versatile tool. I'm regards to Azure and AWS, pick one and learn it. See what the job market is doing where you are located. I chose Azure for various reasons, but also have some AWS certs, but they came after for me. Take advantage of free learnings from both companies
@kubajonkowski7616 Жыл бұрын
Great tutorial. Thank you! :)
@AzureDevOps Жыл бұрын
You're very welcome!
@sophiyaanudeep93977 ай бұрын
Thanks for this video
@roverteam4914 Жыл бұрын
Is it possible to make a careet shift from IT side to Devops...I have experienced in SQL and very little in python...Im doing mostly operating data flow...not developing any part...
@KishanDahiya2165 ай бұрын
It was very complex to understand in pipelines part , all i could make was that pipeline was made to build a docker image then also test it, host it in development environment, then to test and production environment.
@oa3699 Жыл бұрын
Many thanks..
@cryptoeric24 Жыл бұрын
If you have 2 branches off of main and the first branch makes a change, how does the second branch merge in those changes??
@PalleManishi Жыл бұрын
Pull main branch onto the branch needed
@johannes.sbw-media11 ай бұрын
What style board did you create?
@AzureDevOps11 ай бұрын
I personally prefer Kanban style, however you can customize it: learn.microsoft.com/azure/devops/boards/configure-customize?view=azure-devops&tabs=agile-process
@curlybytes2 жыл бұрын
where can we find that option compliance, is that a plugin? whats the name? thanks
@AzureDevOps2 жыл бұрын
Yes, it's available in the marketplace and installed at the Org level. marketplace.visualstudio.com/items?itemName=compliance-internals.onees-repository-banner-prod&targetId=38fb7a48-84f9-449d-9064-29832f2c73f2&ExtHubManageList
@stefanes2 жыл бұрын
@@AzureDevOps "We're sorry, the page you requested cannot be found!" - link wrong or do I need to request it to be shared to my org?
@RazorSPoint2 жыл бұрын
@@AzureDevOps this is not a publicly shared extension unfortunately. I saw it several times with Microsoft in their organizations. I would love to see that available for everyone
@curlybytes Жыл бұрын
@@AzureDevOps Its not avialable to public
@dukeim2 жыл бұрын
Could anyone recommend some course about azure ci/cd pipelines? Nd something integrated with AWS services?
@AzureDevOps2 жыл бұрын
In the video Nana does deploy into Azure and AWS, is there a specific question that you have ?
@dukeim2 жыл бұрын
@@AzureDevOps i would like to learn about the following topics of pipelines menu: pipeline Releases, Environments, Library and Deployment groups.
@AzureDevOps2 жыл бұрын
@@dukeim thank you! I will work on some more content around that soon!!!
@shivakrishnagodugu54302 жыл бұрын
GReAt, Thank you for effort
@barakafun Жыл бұрын
I always like Nana's voice🎉
@aisampayo58492 жыл бұрын
thank you
@AzureDevOps2 жыл бұрын
You're welcome
@chuckdawit3 ай бұрын
Does anyone know where I can get personal help setting up pipelines with my project?
@raghur56782 жыл бұрын
thats a great video ,i have a problem with the Azure artifacts, like when i am running on my feature branch the Tag version is 1.0.1, whn merging with the Develop Branch its getting changed to 271.1.0 ,but i want to be with 1.0.1 version for the Client SDK and the Data N Service Dll... but why its getting changed? any idea.
@AzureDevOps2 жыл бұрын
There's a few things that can play into this. Such as how you're declaring your versions, your branching strategy, etc. Have a read here: cloudblogs.microsoft.com/industry-blog/en-gb/technetuk/2019/06/18/perfecting-continuous-delivery-of-nuget-packages-for-azure-artifacts/#:~:text=As%20soon%20as%20the%20commit%20is%20made%20and,NuGet%20package%20alpha%29%20Pushes%20the%20package%20to%20Artifacts.
@tinyentropy2 жыл бұрын
How does this relate with Github Actions? Isn't the latter one the more recent approach to DevOps?
@AzureDevOps2 жыл бұрын
Hello! This video was strictly focused on Azure DevOps as many organizations are using it and asking ways to skill up their people. You can integrate GH Actions into Azure DevOps as well. Just depends on what you're trying to achieve. There will be some new content around GH Actions coming soon!
@cryptoeric24 Жыл бұрын
Can you edit or delete a branch in azure devops, say you make a spelling error in the branch name
@AzureDevOps Жыл бұрын
Yes! You can edit any branch or delete/add as needed
@2NRVenVR4 ай бұрын
Question concerning the release approval coming from a former Change Manager. Is there a way to request approval from different people based on the criticality of the application being deployed? I'm sure you don't want the same individual approving an "Hello World" app vs a mission critical solution. Can you have multiple people receiving the approve button?
@AlistairDeane-Wake4 ай бұрын
I don't believe this is something you could do entirely from Azure Devops. HOWEVER, I do believe that Azure Devops have some integrations with Power automate. You could most definitely create a flow to request approval in the way you stated.
@jatinnandwani66782 жыл бұрын
Thanks so much
@billionairelifestyle3932 Жыл бұрын
Does it not mean that I should go do software engineering or at least learn necessary programming languages before learning Azure?
@ackrite81392 жыл бұрын
From Zero to Starter
@petrdochvat1442 жыл бұрын
:)
@benb8291 Жыл бұрын
Once you get to starter level you are part of a team project. Your attitude and willingness to contribute towards the project will make you a hero
@raracool04 Жыл бұрын
From zero to being able to work on a team to learn more imo. If you’re looking for advanced knowledge on Azure DevOps it’s better to actually try it in the real world.
@DubaMoorАй бұрын
what is a branch
@KalyanReddy-l5b Жыл бұрын
Hi, I am looking to migrate from TFS Server to latest Azure Devops Server(Not Cloud Services). Can you suggest any tool or material for this?
@johannes.sbw-media11 ай бұрын
Azure Devops Services is missing in our organization, why?
@AzureDevOps11 ай бұрын
You will need to speak to you software admin on this. They need to allocate licenses and grant access.
@bentaybiaHabib11 ай бұрын
Hi guys and @AzureDevOps, I need some help. I am a junior .Net fullsatck developer and I want to understand the relationship between branches and environments. Nana mentioned that when we want to deployDev, deployTest and deployProd, we should trigger the main branch. At my team, everyone works on his own branch then he make a Pull request on azure devops (a request to merge his own branch with the dev branch). At our project, we have three environments (dev, test and prod) and I want to understand what really happen after the feature branches were merged into the dev branch. There will be a merge from dev branch to test branch then to main branch ? Each environemnt will be deployed from each branch or all the environment will be deployed from only the main branch ? Thanks in advance.
@AzureDevOps10 ай бұрын
This depends entirely on your team's setup. We highly recommend short lived features branches. In an ideal world, we often use a main branch with the short lived feature branches, not using a dev, test, etc set of branches as referenced here: learn.microsoft.com/azure/devops/repos/git/git-branching-guidance?view=azure-devops Here's another article that talks about your branching strategy: learn.microsoft.com/azure/devops/repos/tfvc/branch-strategically?view=azure-devops
@villeelomaa78369 ай бұрын
I have used some "old fashioned" on-premises tools for decades. You really have to write code to create a pipeline? No graphical UI for that?
@BitBard302 Жыл бұрын
This is a valuable read. A book I picked up recently that covers the same subject was remarkable. "AWS Unleashed: Mastering Amazon Web Services for Software Engineers" by Harrison Quill
@busyrand11 ай бұрын
Nice overview, however, I hoped it was a genuine tutorial that provided us with the code and assets needed to follow along. I tried to suck it up and create my own assets but got lost and confused too many times. The software is very complex, and I appreciate you all clearing up the fog, but unless my projects were structure like yours I don't have the same options for the same screens. This is my fifth different source to learn this software and nobody has provided their beginning environment, therefore I've gotten lost and frustrated each time. Please, always provide the code/assets used in the video or let us know that it's an overview/demo and not a tutorial.
@AzureDevOps11 ай бұрын
Hello @busyrand 👋 If you look in the description below we did in fact include the repo: github.com/scubaninja/AzureDevOps-Demo. Because Azure DevOps doesn't allow public access to our repo, we hosted it in GitHub so you can have the same access to the code
@busyrand11 ай бұрын
@@AzureDevOps Thanks for the response... I signed up to the mailing list and looked through the links I received but I guess I overlooked it. I'll go back and try again. I wanted to code along with the program and was frustrated that I couldn't... Thanks again...
@AzureDevOps11 ай бұрын
@@busyrand apologies for that. I think some of the links did get updated a bit later.
@MakerB337811 ай бұрын
I have to agree with a number of the comments here in that this is lacking some important details that would make this more of a "tutorial". The area most in need of explanation is the entire pipelines chapter. You never explain how you know what to put where or what the syntax is. You also copy and paste low level SSH commands that don't make any sense and you don't explain them. For instance, the FQIN used in the docker commands includes your repository name twice, and doesn't appear to include the registry or a username. Why? How are we supposed to learn anything when we don't understand what you did? Not to say this isn't a valuable video with a lot of good information, but you could have made it exceptional if you added a few more details.
@narendradc2402 Жыл бұрын
good video. But, the content does not go with the title "Zero to Hero". you could have made this even simpler. I don't think, if anyone without knowing what is devops can follow from the beginning. ask this question for yourself and see if I am wrong. thank you
@adityaprasai Жыл бұрын
Hello, I have a request. In every video I see, people create projects or anything like demo etc. I cant grasp the thought process behind creating different projects. If you could provide an example instead of just creating 'demo' project, it would be very helpful Here are few things about the place I work in. if you could give some suggestions on how to manage the team and work as well as project creation, I would be very grateful 1.) There are limited devs and QA's often meaning a single developer will be working on multiple unrelated work like at once. (Eg They may work on one story for 1-2 hours for story development, another hour for a live bug, another hour for another bug etc) 2.) New requirements comes frequently which leads to potin 1, but we cannot says lets do this later as these might be live bugs that needs immediate effort. But since this happens everyday, planned work never gets done or is very shaky as is done in the last minute. 3.) Currently there is mobile developers, UI developers and Database developers. Mobile developers and UI developers are not related in terms of work. Db developers helps both. 4.) The product has multiple modules (eg, module A has UI and logic for identifying a client , module B has UI and logic for bringing them to sales pipeline and module c has client onboarding to the product ) 5.) Requirements and changes for any story comes almost everyday With this context, how can I do the following 1.) Create a process to manage above issues. 2.) Create projects based on above information. Any suggestions is highly appreciated. If anyone has worked on similar situation, please mention what steps you took to implement and improve process. Please reply if you have any suggestion
@AzureDevOps Жыл бұрын
Thanks for your comment! One of the big things that I see in your structure is that you've divided up your teams into specific roles. One of the biggest features of an agile team is being cross-functional. While that is certainly not an overnight change, it is something we have changed over time with our engineering teams. If you're having changes to your stories, then your backlog grooming and sprint planning is not done properly. Depending on your length of sprints, then this will differ on your team. For example, if you're doing 2 week sprints, then in backlog grooming their needs to be prioritization of what is coming up on the next sprints. For sprint planning, your engineers need to plan and allocate the time required to each task. The engineers need to own the time/effort required for each task for each sprint. Prioritization needs to be considered for your tasks. Bugs also need to be prioritized for each sprint, we used a bug bar. If the bug bar reach a critical point, often we had to assign folks to them during a sprint to maybe tackle one each. But each sprint we use two volunteers (or maybe one, depending on the team), to address bugs during that sprint. Sometimes you need a good old fashioned bug bash. We have much of this documented. Have a look at Agile process guidance: learn.microsoft.com/azure/devops/boards/work-items/guidance/agile-process?view=azure-devops There are a ton of reference docs there to help you :)
@rufelestrada9791 Жыл бұрын
Too bad. This video started out great, then Nana began "talking" through MANY complex pipeline concepts with no explanation or demo. Such a loss.
@WakeAndBacon Жыл бұрын
Is it pronounced CanBan or ConBon…. I’ve been saying ConBon
@AzureDevOps Жыл бұрын
It always depends on accent, but I was taught 'Can-Ban'