DevOps Engineer Full Course 2026 [FREE] | DevOps Engineer Tutorial For Beginners | Simplilearn
Chapters11
Introduces the 2026 DevOps landscape and the course goals covering Azure DevOps, GitHub actions, and containerization.
A practical, hands-on tour of DevOps in 2026, showing how to move from traditional deployments to GitHub-driven pipelines, containerized apps, and cloud-native delivery.
Summary
Simplilearn’s DevOps Engineer course, led by Sinclaire (as referenced in the transcript), maps out how cloud technologies and DevOps are reshaping modern software delivery. The lessons emphasize that DevOps is as much about culture and process as it is about tools, arguing that automation and infrastructure as code unlock faster deployment with fewer bottlenecks. Across the module, you’ll see concrete examples: integrating Azure DevOps, GitHub Actions, and containerization; building CI/CD pipelines; and managing cloud infrastructure through YAML-based workflows. The course also highlights the AZ-400 and AZ-204-style certifications, positioning hands-on cloud environments as a path to real-world readiness. A recurring theme is the evolution from traditional, siloed development and operations to a unified DevOps workflow where infrastructure is provisioned as code and deployments are automated end-to-end. Real-world lab sessions walk through multi-environment deployments (dev, QA, prod) with slot-based app services, deployment centers, and GitHub pipelines. The material repeatedly stresses the benefits of adopting greenfield projects for DevOps adoption, while acknowledging the challenges of brownfield migrations. Throughout, Simplilearn reinforces that the goal is to become a change agent who aligns people, processes, and tools to accelerate delivery while maintaining security and governance.
Key Takeaways
- Automation is the key to faster DevOps: pipelines, YAML workflows, and GitHub actions replace error-prone manual steps.
- Infrastructure as code enables predictable provisioning and repeatable deployments across dev, QA, and prod environments.
- GitHub can serve as a full DevOps platform (repo, CI/CD, boards, collaboration, and AI copiloting) for small teams, with Azure DevOps offering deeper governance for larger orgs.
- Container-based deployment (Docker, Azure Container Registry, and app services) is central to cloud-native delivery and scalable environments.
- Stage-managed deployments (dev/QA/prod) with deployment slots and canary-like practices are essential for risk-managed releases.
- Security and governance stay front-and-center, with topics like credentials, secrets, and access control emphasized in the lab contexts.
- Greenfield projects are the recommended entry point for DevOps adoption to avoid legacy process friction and to maximize adoption success.]
Who Is This For?
Essential viewing for developers and IT pros who are new to DevOps or transitioning to cloud-native pipelines. It’s especially helpful for teams weighing GitHub-driven workflows versus traditional Azure DevOps setups and for anyone preparing for AZ-400/AZ-204-style certifications.
Notable Quotes
"Tools comes last, process and the culture came first."
—Emphasizes that DevOps is about culture and processes, not just tooling.
"You are the person who is going to help organization to set that process."
—Describes the DevOps practitioner as a transformation agent.
"Infrastructure as code which can be a JSON file which can be an YAML file."
—Illustrates IaC as a core DevOps technique.
"GitHub Action can do or run a build but it lacks multi-stage deployment and governance features."
—Points out GitHub Actions limitations vs full DevOps pipelines.
"The course emphasizes a three-stage journey: dev, QA, prod with slots and controlled releases."
—Highlights staged deployments as best practice.
Questions This Video Answers
- How does GitHub Actions compare to Azure DevOps for a small team starting DevOps?
- What are deployment slots and why are they important in Azure App Service?
- What does 'infrastructure as code' mean in practice for DevOps pipelines?
- Can GitHub be used as a complete DevOps platform or is Azure DevOps still necessary for governance?
- What are the advantages of greenfield versus brownfield DevOps projects?
DevOps fundamentalsAzure DevOpsGitHub ActionsContainerizationDockerAzure Container RegistryAzure App ServiceKubernetes (AKS)CI/CD pipelinesInfrastructure as Code (IaC)
Full Transcript
Hey everyone, welcome to the DevOps engineer course by Sinclair. In 2026, cloud technologies and DevOps are transforming the way we build, test, and deploy applications. But how do you keep up with the latest trends and tools in this fast-paced industry? How can you streamline your workflows and become an expert in managing infrastructure, automation, and deployment? Now that's exactly what we will be covering in this course. This course is designed to teach you the core concepts of DevOps including Azure DevOps, GitHub actions, and containerization. You'll be learning how to seamlessly integrate development and operations, automate task, and work with cloud infrastructure to deploy applications efficiently.
But here's the catch. It's not about coding and deploying. We will show you how to automate task with tools like Docker, Azure CLI. Ensure security with Kubernetes and master deployment workflows through GitHub actions. You'll also be gaining hands-on experience working on real world cloud environments, preparing for the AZ 2.4 and AZ 400 certifications. Here's what we'll be covering. First, we will explore DevOps fundamentals and how it brings together development and operations to improve deployment efficiency. Next, we'll look at Azure app services, learning how to deploy applications to various Azure targets like virtual servers and SQL.
We'll also jump into containerization and Docker and how to manage images using Azure container registry. After that, we'll also dive into GitHub actions and automation, how to create YML files to define deployment stages and automate workflows. Finally, we'll discuss environment management focusing on development and staging environments along with security and networking principles to protect your cloud infrastructure. Also, if you are interested in advancing your career in DevOps, the AI enabled DevOps Engineer Master Certificate from Simple Learn is the perfect choice for you. This certificate is more than just a piece of paper. It's recognized credential from IBM and Microsoft.
And here's why this certificate matters. Recognition from industry leaders with certificate from IBM and Microsoft. You show employers that you have the skills needed in today's DevOps world. Now these are trusted names in the tech industry. You'll get practical real world skills. You'll also be gaining hands-on experience in DevOps, DevSec Ops, and AIdriven automation, making you job ready from day one. Earning the certificate makes you stand out to employers, proving that you have both the knowledge and credential to succeed in DevOps. So what are you waiting for? Hurry up and enroll now. The course thing is mentioned below.
Now before we get started, here's a quick quiz question for you. What's the key to a successful DevOps process? Manual deployment, automating workflows, writing long scripts, using a single tool for everything. Let me know your answers in the comment section below. So let's understand the role and that is very very important. For example, when we talk about a debops, the first thing come in our mind that I am talking about technology, I'm talking about tools. This is halftruth. So when we say devops it means that I am talking about a culture I am talking about process and I also talk about tools.
So tools comes last, process and the culture came first. So objective of a deops professional you can think it like you are a change agent who help organization to adopt agile process. Clear out the path to achieve objective. For an example, if I want to cut sort my deployment time by let's say 30% or 40%, it's a very clear objective. Same application when we used to develop and deploy it might take a month. I can shorten that timeline probably by 3 weeks. you are the person who is going to help organization to set that process.
So it's more like a transformation rather than just use a tool to perform an automation. Automation will fail if there is no right process. If there is no right culture. So it means that once you became or call yourself as Azure Deops, you also say that you are the person who can redefine the way our organization is developing application, testing the application and deploying the application. So it's a big task. It's a big you can say kind of a skill anyone have. I can use to work on tool that is a technical part but do I understand the tool.
Now I am going to ask you these three fundamental questions like we always used to do in every module. Number one, what is dev ops? Number two, why dev ops? And number three, Boom. Now, so let me ask a first question to all of you. In your understanding, what is deps? Anyone of you just put in a chat and if you want you can come on mic. Uh development operation for continuous integration. Nagis. Perfect. Very good. Espita development team and operations. Big big big big big big big task. Anything else? Raj Kumar Lik Ramadi. All right.
No worry. So let's understand there is a two world development creation. Okay. One is a developer and second is operation. Hear it very carefully because this is the essence of DevOps. So I'm just putting a name here. Let's say maybe is and I just take one name. I can say Nagis is and administrator. Luggage control Azure cloud. Ispita is developer. Ispita use her development knowledge. Let's say Ispita is a Java developer. Ispita develop a wonderful program and then this program need to deploy on a server on a app on a container but have no control on Azure because Azure is managed by Nagas.
So what is the process happen now? Then ispa raise a request via ticket via other system to create infra where app need to deploy. Now Nages is a very busy person. Nages received this request and said that okay Arita I'm very busy. I will do it on Saturday. What Saturday? I have to reply now. No no Arita I have a lot of things I have to do this task this task. This task I'm not free. can't do anything. Ispita missed the timeline. Why is miss the timeline? Because Nakis not provided the infrastructure in the cloud in time.
Escalation happen. Blame game start. Finally Nagis get a order from his manager. Nages take it on priority. Nages say all right is then Nagis create server or maybe an app or maybe a Kubernetes cluster. Whatever is requirement of our pitha is pitha. So the problem is now these services provided or created by nag nag see it from infra point of view. Nagis have no idea that it's not about a VM. It's about configuration of the VM which probably requested by SPA. He said that you ask me create a VM I give you a BM. No Nes inside a VM you have to enable three services.
You have to en enable RPC. You have to enable HTTPS. You have to enable XY Z. Nag is not a developer. Nages try to configure these services and he misconfigured. When Arpita tried to deploy the service or application on the target, it failed. It failed badly. because there are some prerequisite which is not met in that service and n being a infra guy n do not understand what exactly this serpita is asking every time or go there and click there I'm not a developer so it means that developer and operation is totally not in sync.
They are two different world. So how debop's process now come into the picture? So then in this organization you come into the picture who you are. You are a DevOps professional. You know that in the organization this can be a biggest challenge. Then you set a process. Now here your job is start. You set a process and you say that all right Mr. Nagis Arpita need certain services which is controlled by you. What do you do now? Give Arpita excess of your cloud and in that excess only enable what Arpita can do cannot do. For Arpita for example, Arpita can create a VM with only 80 GB of RAM.
And then Arpita say okay okay okay okay you give me this control access you can give a control access via key via any other authentication method and then arpita use this key and along be with the Java. See also create infrastructure as a code which can be a JSON file which can be an YAML file. So along with the traditional programming language, Espita may use JSON or YAML. And what JSON and YAML do? Espita by sitting at her desk. See run one command and this command execute this JSON script and it will now go and create that target infrastructure with all prerequisite which is spitha want to know and then nag responsibility is only limited to ensure the VM is always running once the provisioning being done.
You should not attack or hack but provisioning the infrastructure along with the code is now this responsibility is merge. So C is dev doing some part of ops. sees dev What it happened now? Now the unnecessary delay which is happening from developer to the administrator that is has been cut short. No bureaucracy in the between. No very long approval discussion chain. No wasting time in hurdle meetings. Ispa need infrastructure. Infrastructure is there. Nages still have a control what she can do, what she cannot do. that he has to ensure that service is always available in hcloud is not compromised and so on.
So I just looking at one very very you can say basic example. Do you feel that in this way your development to deployment can be faster in a state of going through the chain like this? Yes or no? Yes. Sorry. So here the DevOps guy comes right. So he can maintain the so so he is not doing any tool he's only setting a process correct correct so that is what I want to say that is that is important one right because until there is no process it will be a problem tool can be anything correct correct correct correct so this is the very important responsibility raja it means that we have to understand where in our current process this is a problem and then you have to suggest the way out to you know resolve that problem so that your development fast your deployment fast bureaucracy cut in between I hope that right now you are probably have a long of email chain also right your approval chains yeah so that bureaucracy have to be gone if you want to speed up otherwise it will be a problem yeah so yeah Now I give you a three generations that how exactly uh you can say development to deployment happen in a older days and make a note because this is going to be a very very important part.
Now I'm talking about a traditional development environment company who do not use DevOps what they do. So the first flow start with uh you know the a source code development. To develop a source code you have a 100 of languages. For example you can use Java, you can use Python, you can use it you can use react. So as a developer how we do that we first develop our source code then possibly we can also run our unit test here function by function we test it. So you can say that source code plus unit test at happen at development level.
Then developer once the whole program develop unit test is clear they share this code with uh you can say your testing team. Now testing team use various type of testing tool. For example, a popular testing tool if you know it's a JUnit. It can be XUnit. It can be selenium. It can be MS build. uh sorry MS test I mean to say there are multiple tools available where the testing team do the testing and then once the test finish that artifact now send to a deployment deployment team may use tools. For example, one of the very popular tool is called BMC Serena.
So using this tool your artifact which can be a zip file, jar file or war file go and push to your target environment and target environment in the old time is only one thing is server. It can be your Dell server, it can be your HP server and this is how the process happened. Now you are a debops person. So you may ask a question once as a developer we update our code where that update code gone where it safe or do you overwrite the existing code in a traditional development environment it is a overwrite.
It means that whatever changes we make it will be override and we do not have a traces of what we done in a previous time. So how you now approach this whole approach? You make a very small you can say uh introduction of the first Debops tool. Same environment and now you are moving your organization to the Deops stage one. And what you do in a DevOps stage, you simply say that once my once developer finish their code with unit test, the code will now go to some kind of a central repository. So now you are first time introducing a source code management service which can be a GitHub, a GitLab, a subverser.
Why we should go with this approach? Because if you introduce a full Debops flow in one go 90% chances it will fail people will not adopt it correctly. So I start with the first say Debops one we are going to introduce SEM tool let the people to now adopt this practice and when this practice adopted that every source code could now go and sit in the SCM where it maintain the version of the code then you introduce probably a second tool and what is second tool you say that now I am going going to introduce a build tool because build means it is going to create something called package test your code is bug free and so on and there are many build tool available for example Example, we can use a build like genkins if you heard of like MS build like maven like a new gate.
Now these are the few popular name people use it for build process. Now once the build created it go to test and then test will take to the deployment. This is we called debops stage one. Once people are now accommodated themsel with this process, we are now going to move to a deops stage two. And what we do in a deops stage two. We now going to introduce one more tool after the test and we call it as an release tool. So it means that now we want to control which version to release so that if something goes wrong in the deployment you have a roll back option to roll back to your previous releases.
And to do a release again there are lot of tool available for an example we have option to use enible here we can use chief puppet and so on. So it means that if you work on traditional DevOps practices, you might see this type of process. And many company they once they mature they automate process from build test to deploy all three by creating something called a deployment pipeline. And the tool which support this deployment pipeline very popularly known as Jenkins and very popularly you can say known as circle CI But you are once you see your organization is move and adopt the whole end to end automation process.
Now you probably decide to take your company to the next stage and that is the final journey of the whole transformation exercise. We call it as in Deops stage three. which is a current stage and in this current stage we have everything same what we are replacing now I say that in a state of using public git repository we can now have same git same command, same functionality but it is very very restricted to my company only is other can't access it and this is called Azure repo same g. So while using it you hardly notice any difference but now it is very very restricted to your company only.
Other cannot see that other cannot access it. No problem. While your MS build maven as a build process as a build behind tool is same. You just use automation tool change the automation tool. So there is no genkins use same configuration which is your build tools remain same because that need to be installed in your environment. But what we are going to use now we are going to use now a build pipeline. No installation not like genkins you have to install it on a server then you have to do configuration pure SAS platform just click ready to For a test you can use for your test you use same back end JUnit, XUnit, Selenium and MS test.
But to write your test cases collect the report of your text thesis, you can use test to release and create a release artifact In the state of a niblef we now going to use same pipeline but it is now instead of a build we are going to use release pipeline. Now your deployment we do not need BMC Serena. You can simply use your release process the release artifact which is created by the release can be either automate or you can just have a single click button it will whole application going to deploy. In in fact if you want you can also create an infrastructure in the target environment.
Now all this tool which you see from here to the deployment none of the tool we have to install is come with the preconfigured environment and service which provide all these tools we call it as an Azure Deops tool. We are going to explore it as I said in a class number 6 7 and 8. But at this point of time this tool this tool actually create a magic and it will take lot of task you know lot of task of the administrator. Yes, lot of task of the administrator which need to create a server then install genkins or encel or this or that.
Finish gone. Single click done. Just like we do in and what we get additional advantage now in a cloud. This traditional server gone and instead of a traditional server your target environment can include a wide variety of services. It can be a VM. It can be an app service. It can be an Kubernetes cluster or you can say any of the container service and many more many more. So I mean to say if you look at the way everything is transformed you can say from or traditional to if organization decide to move to Debop stage three which is a pure cloudbased you can say automation tool.
It everything is clear. Any questions? Bola, Dominar, Nagis, Espita, Grog, Lalit. Huh? Git action can do or run a build but yes all good same Oliver same so for scripting option also you create your YAML script send to the SCM either you can use the build test is not required for scripting or you can directly release Exactly same process. It can be your terapform script. It can be your encript. It can be your Azure ARM script or bicep script in Azure. Okay. So, Grogi remember the GitHub action which we are going to see today again.
It lack multiple thing. For example, approval. reporting. Number three, it doesn't create the process which I am showing you right now. For example, you have a build, then you have a test, then you have a release and GitHub also not give you an option to use your own infrastructure means let's say you want you decide to use virtual server which loaded with the This is not possible. You have to use only GitHub. So in the short no reporting you cannot create a multi-stage deployment lot of lack of lot of security control for example if you want to introduce authorization if you want to probably sanitize the target before deployment that it is matching your standard organization and compliances not this checks and balances not there.
Yes. Bola now you are getting that. Yeah. Yes. So all this process end to end is done by the debops team. So actually now if you look at that developer task, build build engineer task, tester task, release task, deployment engineer task, everything is now consolidated. You have a single tool. Make sense? You have a single tool instead of going through all this and later on we will explore more you it also have a project management tool where you can manage the overall project visibility through canban board. Why it is booming across industry? Everyone is now say that in my company we are going to use DevOps.
We are going to use Debops. Any idea what is a main triggering point? If you can just guess off for example what has changed you can say in last couple of years cloud huh digital cloud is booming. Yes. This is Nagis of O of course. Yes. Entire project. Entire project. Yes. Yes. Automation and less build time. Exactly. Exactly. Automation Arati. Exactly. But I still questions same question. Okay, just give me one second. Just one second. Agile work culture is pita. Yes. Very good. Very good. But we have a question still there. Right. DevOps is not a new service, right?
It's not a new process. DevOps exist for almost like 18 20 years now. So why the benefit of debops not realized by industry I can say five to seven years back and why every industry is now coming back and saying that I I am going to use DevOps. Deops was there for a very long time. For example, Genkins tool available from last 15 years. I give you a scenario. Yes. like this. So you can give you a scenario. I think that everywhere when you take uh let's say India or any other country. Yeah. Bola. Yeah.
Yeah. Exactly. So let me ask one question. For example, if we have to order food, if we want to eat something, what we do? Should we go to restaurant and should we order from online? If we want have a dinner, should we go to restant or order using app? What you do now? Any one of you can answer this question or using app right visual. Yeah, I'm giving an example now. Let's say this is your food aggregator platform. You can take any name in your country which provide a similar service is a food agreeator app.
It can be Uber. It can be Netflix. It can be your your favorite bank. It can be anything. Now this app is developed by your developer. Perfect. And look at the whole process. What happened now? So you actually it's aggregator app. Now you have vendors restaurant. So let's say one of the vendor or one of the restaurant is sending an update. All right. I have now new pizza available for all of you. So it means that in this app this update must be reflected then only people can see that another vendor they now announce 1413.
If you order one pizza, I will deliver another pa 1 + 1. You can say 1 + 1 free. It must be so in your app. Then only user can avail. And let's say you have a third vendor, vendor number three. They said that sorry and a specific food item is not available. Let's say hot dog not available. And this aggregator app is not talking about one vendor. There are thousand vendor. Each vendor is continuously sending an update. And you have a very small development team. What your development team be doing? Look at the development team point of view.
development team quickly update the code. Each update they will update the code. Then it goes to a build. code get build code get deploy and where it deploy first it might be deploy to a test Once the this is pass then it will go to your probably QA environment just to ensure everything in the app work. Lot of people internally check this application. Even vendor participate they check yes it is visual. Then we'll finally go to your production app. If you have to handle thousand app thousand updates every day, thousand updates, how big your team look like?
How many developer you need? How many build engineer you need? How many tester you need? How many deployment person you need in a company? You have to handle thousand update every day. Anyone? How many build team we need? How many deployment team we need? How many tester we need? Probably we need two 300 people. Yes or no? Because one develop the code, one run the build, one deploy in a test environment, one is checking everything and it's not about one, it's about thousand update coming continuously. Correct. take their team you hardly find it's more than you know like a you have a 10 people 20 people so maybe I can say that it is only have a a 10 people team out of 10 people maybe five is developer rest are the ops Correct.
So how this is possible because to run a build command run a build command you have to run a build you have to wait to do a testing you again have to run a you have to wait and I'm talking about lot of updates keep coming now whole site work. Just give one second. I use DevOps once developer update the code build deploy test everything is automated everything done by machine everything is done by machine everything is done by tool only developer have to work that's Make sense now why debop suddenly you get popup now it's our world has changed as an appdriven world everything is happening Bank is app based.
Government is app based. You want to buy a car app base. Go to bank app base. Watch a film app base. Yes or no. So that is the one of the reason why you suddenly because app is now became a de facto and this app need to be constant update. And to make a constant update we need a huge team member that is going to be a additate cost. So that is how the tool going to make everything faster. Now you clearly understand why we use DevOps now. Why DevOps boom now? Because we as a customer, we as a consumer we change our you know behavior.
We do not like to go outside. We want to order everything through app and that app need a constant update. Buoindor. Yeah. So this is very very important one. Now we understand as of now what is Deops. We also understand why DevOps boom. Now now let's go to the next stage. So for an example when we say I want to introduce Debops in my company if I want to use a DevOps and you are the change agent what will you do? So the very very first thing you have to take care take care about overhauling the whole process and where will you introduce this device?
Please look at your project. Now your project can be an existing project. Existing project which I mean which I mean the project which is already running in Microsoft world we called such project as a brownfield project. Be careful when you try to introduce DevOps process in running project because it create lot of challenges and issues. Microsoft suggest if you are first time introducing DevOps in your organization use roll out DevOps tool with new We called such project as green field project. So Microsoft recommend if you want to use your deops file please use it for green field introducing deops tool in between running project it can be create a chaos it might create a issues Because your old project may have a lot of technical burdens, issues.
Even if you want to introduce in the running project, do not introduce the whole step in one single go. Go a step by step. Start introducing source code GitHub. Then introduce build gradually. So now I'm going to give you an example of an existing project and then we see that how we are going to use tableops stage one to do this whole project end to end. This is my current running project. In a current running project, I have a developer. This developer, let's say it's a net developer. So, it use a net code. Develop a net code with help of an ID like a visual studio.
And then from this they deploy this whole code to Microsoft Azure. Let's say they deploy it on Azure app service. This is current scenario. Developer directly from their local machine. They push this code to app service and you are now a DevOps person. How you are going to now just by introducing one single tool and changing the process you are now alter the whole you can say dynamics number one what the first issues you are able to identify here in this process from a development to target environment. What are process you identify or issues you identify?
Vijal Bola is Dindor Nagis Lalit. What is the current problem in this process? Raj Kumar Arati I'm asking that this is current process you are a deops Identify issues in development deployment because first of all you have to identify the issues and once the issues identify then only you can suggest your suggestions right. Huh. Limitation of the dev managing Azure service. More time required. Really code is not tested. Nages. Yes. Yes. Very good. Directly deploying the code. Exactly. That is our I'm just giving an example. Okay. And just let's see if you can able to example.
So just opening one of my code where we want to deploy my service this is my code. I'm just launching my development environment. So I'm saying code space dot and now my V code is up and running. I have developed this wonderful code with me and if I want to deploy on Microsoft Azure let's an app service I can go to the extension of the VS code and I simply install SDK of an app service and once that SDK installed I can go and connect Microsoft Azure uh Mecca call the exactly now what is the problem if I make let's say if I make in this exchange and I deploy So after making a change, I simply make it uh go and deploy this code to the target.
My audio is breaking. Just confirm if my audio is breaking quickly. Okay. Okay. Perfect. Okay. Okay. Ready? Okay. All right. So I'm saying that I just make a change here and I deploy my code. Next time I make another change. This is demo again. Save and deploy it. Now can I recover my old code because it is overritten now. Yes or no? Can I recover the old code? No. Because I have already overwrite it. Now let's say for an example I want that some portion of the code. You should now develop some part of the code.
You are a different developer and you now want to make uh contribute in this code. How I can share my code to you? It is in my local laptop. Can I share the code with you? Yes or No. So actually if you look at that you have no exactly you have but two two bigger issues in this whole process. Number one, there is no version we can say changes managed. It's a simply overwrite. Uh this is simple uh Olivia. This is a VS code or any ID you get extension. In that extension you can see if you want to deploy it in Azure app service, Azure functions or any other Azure services you have to simply click it and you get a install option.
So when you install extension it can be Azure it can be AWS also you will get the icon of Azure here you see that and when you have a icon you get a sign in button just look at that this is how you can see all your services now once you authenticate is that clear Oliver extension install extension and then you should able to see the icon like Azure AWS. Click that icon you get a sign in option. Click sign in and you are connected. Yeah. Yeah. Perfect. So look at the problem here. In this issues there is no code version maintenance.
So you cannot record the changes. Second, one developer cannot share code with other as application code in their local laptop or local machine you can Okay. The third issues which we identify it directly deploy production app service. So if anything goes wrong everyone impacted now okay okay I will I will just share okay later on but at this point of time it is you know these are the three big issues everyone agree it is a three issue number one issue number two issue number three yes Now what will you do if you want to introduce DevOps in this process?
The first tool SCM door version control very good. So now I am going to introduce one process in the whole setup. I said that okay here developer here developer you develop your code you are wonderful people should develop your code and after develop your code remember tomorrow we are going to see a full GitHub in a more detail but at this point of time developer once they develop the code put this code in Ghub. So in a GitHub they have something called repository. You can think it like a folder. Usually we called this repostory as a main or master repository.
So your code now from local machine will go and sit into GitHub which is a cloud tool, cloud repository tool and in a more a specific technical word we say checked in code to SCM. This is how we use our more terminology. This is how the developer do and the code is now available on GitHub. And then we have a target environment. Right? This is target environment which is in a business. Since you already done AJ 104 and many of you are 2204 also I hope that you understand this is a service which is platform as a service.
So when we talk about this service, it basically provide you a different environment. So now I am going to say that this app service is actually have a dev environment, development environment. And when we say it is a dev environment, also give me one URL which like a dev dot simply learn.com for an example. Now this dev URL access by only 10 15 people and they mostly belong to a IT or development team. It is not known to the outsider world. I'm just saying that only 10 user know this environment only 10 user then we create another environment just like this let's say we call it as a QA environment and last one is a prod environment So now everyone have a different URL.
For example, the second environment will have a environment called QA. Third have a environment called simplylearn.com. No dev no prod because it's a final one. Dave environment is known to only 10 user 15 user within a company and mostly the developer or IT people. QA environment is available to a large set of people let's say 200 user which include your IT people nonIT people or maybe some sample user who probably test your application. So because you now expand your user base you get better feedback how your application look like and your public URL is known to the whole world millions of user.
So now from GitHub we have to integrate our dev environment. the process of integrating my GitHub to the dev environment. We can use CI/CD process or we can use push base you can say changes. So in our case we are going to use Push base means whenever the code get update sorry it's a pull base changes. So whenever the code update happen at a GitHub we have to pull this code updated code in my dev environment. Let the 10 user access this URL and they can test everything now and then from the dev environment we can swap the whole code.
Swap means it will do simply cut and paste. Swap the whole code from dev to the QA. And now from QA we are going to do a further swiping to the prod environment. Does it make difference between this traditional? So now you have a code version. Every code when you change you have a version because it is in a GitHub. So you can share this code with any other developer and instead of putting it into the production application service I am now have a staged environment dev QA and a prompt. So three problem we identify just confirm are be able to solve these three problem.
Yeah. And you have an option to click create. You see a babe app. When you click create, you see a babe app. Babe app. The first option. Please click babe. Babe app. Every one of you. And in the resource group, look at the screen. You should able to see ODL. Select the ODL. So I don't I don't have ODL. This is personal account but yeah. So in the resource group drop down you select ODL in the name. Type your name in a small letter. Yeah Oliver. Very good. Type your name in a small letter and then type app and if the app and below you should see a check box which says secure unique default host name uncheck it and just confirm if your name is accepted.
If not may you can use some number like in Gregory case it's a tailor app0709 something then in the runtime stack drop-down and select ASP.NET version 4.8 8 ASP.NET version 4.8. In the region, always select West US2. Um, I'm going to select US cuz I'm in the US side. Um, remember we did we tried to do this before and it wasn't using West US for some reason. So, I just I do the one I know works. Yeah. Okay. Everyone use west US. Okay, West US in Windows plan I think you already have just click create new just type demo demo and remember to delete demo.
Okay. Later on. Okay. Okay. And just confirm in the pricing plan if you drop it down. You see lot of plan like a free basic premium. Everyone just can you confirm you are able to see lot of plan free basic Yes. So just below the plan just below the plan there is a explore pricing plan. Just below the plan there is a option called explore pricing plan. Click it. You should be in the same screen. I scroll down till last and you should able to see under legacy a standard S1. Please select the standard S1.
Confirm if you select a standard S1 all of you. Rati, Rajumar, Espita, Bola, Oliver, Lalith, Dindor. Yeah. Yeah. Yeah. Click select now and hit review and create. Why did we pick standard S1? Because we want to create three stages, right? Dave, test and Yeah. Click create. There's a lot of just confirm once your deployment complete in the chat box. Oliver. Okay. Very good. Hope there is no error for anyone. Lindor, congrats. Oh, Oliver. Okay. Bola. Uh Kota. Okay. Oliver, you please change another region. If you select West US2, select West US probably West Europe again.
Relaunch it again again. Create again or can you stop for a minute? Let me go to Over. I think that he first Okay. And then I come back to you. Can you share your screen one more time? Oliver share the screen more time. Bola complete domain complete. I hope for Nag also it is complete. Arati Oliver please share your screen. Espita very good in progress. Okay, good. No worry. Oliver, are you sharing screen? Congress buddy I do okay you if you remember it's good let me go to Grog in the meantime yeah Grog I think uh Oliver say he will do by himself I think I'm able to see Oliver screen yes Oliver okay create web app very good you want me to share You just just hold on a minute.
Yeah, just type some name. I'll stop sharing it. Okay. And then you uncheck the box which says secure unique host name. On the top you have a box. We have a check box which says secure unique host name. Oliver just below the name. No no just below the name there is a check box called secure unique. Huh? Uncheck it. Yes. Very good. And last time you try in East US or West US? If you try in a West US, East US, please change to West US. West US 2. West US 2, not East US. Aha.
Exactly. Yeah. And in the plan, in the plan, explore pricing plan select S1 from last. Wait, wait, let it come. I think the first one is S1. If you are able to select under legacy, the first option is a standard. Yes. Very good. Yes. Click select. Uh, and that's it. Hit review create. Let's see if it work. Create. Oh, that's fine. That's fine. Click create. Hope Oliver you remember this step because we are going to use it multiple times during our DevOps lab. Let wait let the deployment to complete. Hi done. Click go to resource Oliver.
Excellent. Now on the left hand side you get default domain. Right hand side. Right hand side there is a default domain. There is a URL. Right hand side. right hand side. Ah, copy it. Paste it in the browser. Yes, you are in correctly now. Right. Okay. I stop your sharing Oliver. Now I am going to Grogy screen and then you can follow whatever we do there in Goggy screen. Okay everyone. So let me go back to share. Yes. Yes. Let me to stop sharing. Yes. Everyone please watch carefully a Grogary screen and then we can just follow as it is just step by step.
Okay. Um so the the web app was ready. I just I just opened it. I can go back to the resource group if needed. I think Raj Kumar also Okay. Raj Kumar just hold for a minute. Let me finish it here then I come back to you. Okay. So on the left hand side on the uh sorry right hand side you have a default domain. Copy it. Oh yeah. Okay. paste it in the browser. This is your production URL. What we all This is your production URL. Okay, it has nothing. It's just a basic content.
Now go back to the app service. And then on the left hand side everyone you see there is a deployment option. On the left hand side you have a lot of menu and deployment. Under deployment you should see deployment slot. I hope all of you are in deployment slot And then you get an option called add a slot. Yeah. Okay. Click add a slot. What is my first slot? Dev. So type dev in a small letter only dev and look at the URL. Are you able to see the change in the URL? It say Taylor append dev.
Right? Just below the dev box you see the URL. Get copy the URL. Everyone copy this URL. and click add. No, you have to add it first. Mhm. And click add. It will take couple of minutes. So, just wait. This is your dev environment, right? Now Sarati just confirm if your div environment is also created. Epista Oliver Bola. Very good. Yes, exactly. Okay. So now you just paste the URL in the second tab of your browser and confirm it is working. You get similar content. Hit enter. So your production URL and the DV URL exactly look same no change right?
Now go ahead and create one more slot. Nothing new right? Yes exactly. Go ahead and you add another slot called QA which is for quality assurance and copy the URL one more time and click add. And now you should able to see three Dave and a QA correct correctly production. See yes but um the QA is still processing processing. Yeah. And now you can test the key URL that is also same right. Yes, I hope that it's fine. Can you stop your sharing for a minute? Uh they're all the same so far. Yeah. Uh exactly.
So just wait then we will now push our code to one of the slot and then we see how it work. Raj Kumar share your screen Done. Wow, that's Raja. Yes. Hold on. Let me run. So, can you just go to basic for a minute? Uh, Rajan, just to see. Let's scroll down. WS2 standard. Huh? Just I think that this will work. Click review and create. Hopefully it work. Create. We are doing Raj Kumar exactly production-l like setup. Okay. This is how probably you see in your environment as well. Hold on, hold on, hold on, hold on, hold on.
I think that for you only East US is allowed. Can you click basic and change to East US2? Go to basic basic basic east US2 and select the standard platform. I hope uh Rashimar you are also using AJ 400 lab not the AJ 104 because 104 it is not allowed. Click review and create. No, it's Can you show me your LMS? Which lab you are uh hitting? Go to LMS. Oh then it's work. Uh can you unmute yourself in 104 which location you generally select? You remember? Yes sir. If you scroll down and maybe you can try East US only.
Try differently selected last first time. Yes. 104. Ah 104. Huh? Yeah. No no no change. Yes. But the only problem is Rajumar in 10 in East US. Now you hardly get the option. Click uh to select S. Then I will go bit alternate. You may not do the full lab but at least you do partial lab. Okay. Click the check box. First one select review and create created by tag. Can you show me basic one more time just for a curiosity? Okay sir. And scroll down. Scroll down. Scroll down. And in the Windows plan can you drop down?
Ah that's fine. That's fine. Okay. Try Why there is so many restriction in your account? create it there right created by I think make the seek created by Can you click that? Let's check. Click. Click. Okay. So try one more time. Uh in case if it doesn't work for you Rajan uh most probably you just raise one support ticket with this screenshot. Okay. You have to resolve it before maybe the class number three. Try create again last time. No, I think that for you this is a problem. Okay, just take this screenshot and raise the support ticket and just enjoy the lab.
Okay, Rajar. Yeah, sure. Yes. Sorry. Can you come back? Uh, Grogi, now we are going to do the final one. Ouch. Um, yes, I'm starting to share my screen. Okay. Um, go back to everyone. Go back to Azure. In Azure, in Azure, go back to deployment slot and click the dev and click your dev and just confirm. If you are in a dev, can you highlight the dev name on the top left hand side top? Just confirm all of you are in a dev only. Look at the screen of Gogri. Arati, Oliver, Bola, Dominor. Yeah, very good.
Oliver just confirm. Okay. Okay. Then I ask Gregory to probably help you out. Okay. Okay. So you see the dev now and then on the left hand side you see deployment. Click deployment please. Then you hold on Oliver for a minute. Click deployment center. Everyone click deployment center. Just confirm if you all are in deployment center. Yeah. Okay, now everyone go back to GitHub as fast as you can everyone go back to your GitHub and probably uh Oliver you can also do and maybe Raj Kumar you also do at least this part for your future lab.
Everyone go back to your GitHub and then look at extreme right hand side top you see your user account icon. Click the user account icon and there is a drop-down. You see a drop-down in the drop-down there is a setting Just confirm if you all are able to see the setting option. Nindor Oliver Vijal I hope that you are also doing Rajumar. Yeahi isa I think Nages you already did but anyhow just you can check okay click the setting now. Yeah, click setting and on the left hand side scroll down till last and you get developer setting.
Just confirm if you are able to see developer setting in your GitHub extreme last on the left hand side, right? Yes. Click developer setting please all of you and then you should able to see personal access token personal access token and in the personal access token you should able to see token classic token classic click token classic And you get an option called generate new token. Now be very careful here. You have a drop-down. Click drop-down from the generate new token and you get generate new token classic. Token classic. Yes. Click generate new token classic.
If you have to authenticate, please do Now you are in the same screen just probably you can give a note AJ400 so that you remember now this token is valid for next 30 days and you now check every box like repo check workflow Check. Write check. Delete. Check. Please check every box. Everyone click the log and just confirm what is the status you are seeing. Running, fail or deployed. If it is running the fourth column which say running deployment. If it is a running deployment, congratulation. You are done. Good job. preparing deployment. Okay, very good.
Quick question. So the key that we created is it so once it's only valid for 20 days, but I think that's what you said. So after the 20 days, does this go away or it has to be done again? Go away. Yes. No, this go away. Then you have to disconnect it and again have to reconfigure the setting. But in a production usually because we using debuffs so we do not have to do anything here we use in a deos tool pending. How many of you see succeeded message once you refresh it? So once it is done I will show you what will happen.
If you go back to your dev URL, can you go to the dev URL? You already have in no in the browser you already have. Okay. Okay. Okay. Sorry. Let's Sorry. Sorry. Sorry. Dev one. It is product. Uhhuh. Refresh it. When you go and refresh your dev URL, you should able to see our live code is now here. Uh and then in the branch type master excuse me sir professor just really quick where it says external get there's also says like Azure repo is that for the the Azure dev devops yes the devops yes go I scroll up I'll just click save did you wait the safe to be happen.
Okay, no worries. So, Raj Kumar, you may have to just uh you you in the LMS now there is a right hand side top there is a help button. Click help raise a support ticket. Hopefully by Monday it will be resolved. At least by next class you should be ready. Okay, perfect. Now you just go left side up left side go to overview overview first option you get a URL okay click that URL right hand side there is a bizu ah yeah bizu ah exactly very good yes paste it yeah so it will give you first default uh just Say continue to the site.
Continue to the site. Yeah. Now go back to uh it will loading. Go back to your app service resume. And then come back to deployment center one more time. And you see the logs. Click logs. So you you say that it's showing generating deployment correct and you have a refresh button on the top. So you have to refresh it after 1 2 minute you should able to see succeeded option. Once succeeded if you go back to your app service bizu and when you refresh it it will show you your my go to app service on the browser.
So you already know you already pasted huh? So this is this content will change right? You will see my app my code. Okay now so just you have to wait till the succeeded will happen and in in the meantime because you cannot create the slot. So just watch the next screen of what we are going to do in a final time. Okay. Yeah. I stop saying and you keep refreshing till the time you see the deployment succeeded and then confirm in the chat once you done that. Yeah. Grogi see. Yes. Final everyone. Now I am going.
Everyone just watch. Raj Kumar you also watch. Please go back to app service. All of you. So in the dev you see that it is running. If you go to the UAT and prod just confirm you still getting the old code. Go and refresh everyone the URL of UAT and prod and just confirm if you are getting the same code. Go back to the URL you have pasted already. please refresh all three URL and you just confirm you only see the content in dev not in a QA not in a prod. Can you refresh the prod and QA also prod you have it second ah exactly same old code everyone able to see same old code right correct Arati yeah exactly so what we do swap go back to your uh Azure everyone go back come back to except Except my new friend Vizal right.
So V you you cannot do that. So you just have to watch. Okay. So when you come to deployment slot everyone come to deployment slot and you when you click this deployment slot you should able to see swipe option. And second very important part why any company go for a devops if you look at a segment of the companies only 7% company worldwide 7% only 7%. We call it as a technology company. Rest 93% company has nothing to do with technology. Like Hyundai they manufactured car, American Express they are dealing in finance. If you are in India, you have a food app like a gumato, a food aggregator.
But still almost every company if you go you found they use DevOps and you wonder why. So if I want to purchase let's say if if I am working in a BMW BMW is a luxurious car manufacturer and inside the BMW I am able to see there is a devops. So one very important part is today world today world is a purely appdriven world. Look at that how I and you connected today. You are sitting at comfort of your home or office. I am sitting at the comfort of my home and we both are connected and talk just like that we are there in the same room.
How this is possible? Can anyone of you imagine this type of scenario 10 years back or 5 years back? No. Because internet speed was just like a 2G and today we are living in the world where we already have a 5G and there is already a planning going on for a 6G huge speed. So this huge speed power a smart devices even if you go to a very small town or a village in any of the country you surprise that the people carry a smartphone and they try to do everything from from the mobile how this is possible that application load fast when you do something it will just go to the vendor site and perform the transaction speed.
So this speed trigger company to go digital when we go say digital just look at the way how we are doing How many of you stop going to the bank physically? I think all of you. You hardly visit the bank branch. How many of you regularly go to the restant? Probably hardly. If you want to use any government service, how many of you go to the government offices? probably very less because now we have a app through which we can connect to the government and yesterday I get a call from a Hyundai car that sir do you want a car I say I cannot come I do not have a time they said do not need to come I will show you the car model I will give you a virtual experience So that you can see how the car work, how the car look and if you have any question just ask me digitally.
this app change customer behavior. People like me and you, we do not want to go outside now. We say that we are at home and I want everything. And that is the reason why any company whether it is a product company whether it is a service company whether it is a they now coming with app and yesterday we just discussed one app any food aggregator app in your country like in India you have a gumato now this gumato app receive upper ordered from thousand of vendor every hour. Now I have this food available. I now offering discount now this food is out of stock and these update should available to your app in a real time.
So to handle thousand of the updates, how many developer we want, how many build team we want, how much deployment team we need, how many tester we need just you can imagine that but you will wonder that when you go to let's say any food aggregator office you see that they have hardly 10 people out of 10 maybe five developer rest five they are able to handle everything. They can do a testing regular time and this is how you see the devops coming into the picture. They said that once developer finish their job, we can use build, we can use test, we can use deploy everything in just a sequence.
Second, as a company, as an organization, when you are planning to use DevOps, you should go with existing project not recommended because in existing project if you introduce DevOps process, it might create a chaos. So, Microsoft recommend that you should go with a green field project. The project which is going to start now you should reset the process and probably you can have a process like developer develop the code go to the SCM from there it will go to the build tool from there it will go to the testing from there it will go to the release service and from there it will go to the So it is a high recommendation that when you have a green field project you should go with DevOps.
And then we done one wonderful lab yesterday where we actually tried to simulate real where application get deployed in a dev QA and a prod through pullb means your app service pull and do all these background tasks. So as we discussed yesterday that in a traditional development environment this is how they work. You have a developer who developed a test source code. Do you have a tester who use the different tools to test and then it will pick up by the deployment team. So if organization try to move from traditional way of working they likely to go with a debops stage In a debops stage one they might a very first service called GitHub.
And this GitHub probably is a best way to introduce DevOps in organization if they never use automation tool. So today we are going to understand SCM especially the GitHub how important it is? Yes Nag I think you have a question. Hold hold hold on. Uh yes sir. Yesterday we have uh created Azure app service with three deployment slots. three environment QA de and the production. So are we like Azour going to charge only for one app services? Uh not charge for app service. Azure will charge for compute. Remember when you use basic it means that you get one server with certain amount of compute which like a one one GB RAM and uh one CPU.
So you run one app service, you run 10 app service. Microsoft doesn't matter. They said I will charge you. Okay. Not for the even if you are having multiple events that is that doesn't matter then. It doesn't matter. Okay. Okay. Okay sir. Thanks sir. let's understand first before we discuss world of SCM like a GitHub how exact end to end debops flow look like. So for an example if I give you A little basic idea that the very first come with developer or you can say a people who develop a source code. So there is not one developer, there is not two developer.
There can be a multiple developer who work as a team to develop one So let's assume that in a typical company we have a three and let's say this three developer try to develop MS office. So developer one probably Excel developer to let's say develop MS WD might develop another one which is called PowerPoint three different developer work on a same project. Project is called MS office. So to develop MS office probably the work divided to three developer one develop excel one word one powerpoint and just to make the life more easy let me make just put a name here so let's say for example this is let's say Arati one of the developer let's say for example Ispita second developer and let's say Rajkumar third developer They might sit in a same office.
They might sit in a different geographical location. What happened now? So all these three people after develop their part of application. They push their application code to GitHub and in a GitHub they might have a main central repository. Let's for an example I say that this repository is a master or we also sometimes call it as a main Let's see that this GitHub managed by another person we called that person by designation SCM master. So for an example let's say this is done by SEM master is domain. So door then ask Arati is pitha and rajumar.
Hey Arati. Hey Spita, hey Rajumar, you cannot push any of your code here because this code is not complete. Your project is not complete. So what it does now then they create three special branch. Let's say inside the GitHub this is branch one. You can say just inside this there is a one a small folder and say hey Arati you push your folder your data here. Ispar this is for you and Raj Kumar this is for you. In a very technical word, we call it a child branch. People also call it as a feature branch.
But just for understanding let's keep it simple. So what Arati do now? Then Arati push her part of application from this local machine with help of something called get client on this branch. So code move from here to here. Exactly same thing happened by Ispita and exactly same thing happened by Rajumar. And this process of pushing the their part of the code from local machine to their respective branches. We called this process check in process. You can call it as a push also. somebody you can say technical terminology. Every developer then checked in their their repository.
Once their code reach here then there is one more person introduce you call that person your team lead you call that person is a senior developer you just name it so let's say for just understanding purpose I'm saying that Prattab is a senior developer. So Prattab then review the code. Which code? Arati code first. If they found everything is correct, then they merge this code from this branch to this branch. And in a technical word this process in GitHub we call it as a merge process. Then again they perform the complete review both MSW and Excel and when they satisfy they again merge from here to here.
When you say merge means this repository actually go whatever they have is gone and it will come to the second Post that when every is now inside one branch then they decide then they decide to merge this last branch with the master branch. Who is doing all this task? Which parab senior developer? So now you have complete MS office as an application You can say from your local repository to now finally it come to the main Now you have a perfect process where you Perfect. Now, so now the code finally merge and available in the master branch.
Now from here from here this whole code need to go in build process. So from developer code already come to the master branch and from master branch the code must go into the build process. So now you should need a build tool. Now this build tool can be anything. This build tool can be gen. This build tool can be. This build tool can be Azure build pipeline. This build can be workflow or GitHub action. So for example, you can use GitHub action or GitHub workflow to completely do a build process. Oh my god. Or you can also call it as an GitHub action.
So I mean to say if you look oh let me to put it like this get workflow or we also call it as an action. You just name it and but this is how this whole process work or you can use Azure DevOps build pipeline Dev Ops or you can use a third party service. It can be genin or you can use genkins circle CI. So usually these build tool already have an authorization. We have just seen a study in during our lab exercise that other services from outside connected with your GitHub and in a very technical language.
This type of relationship from my GitHub other service we also call it as a babe hook. It create a hook from me to you. There is a hook. Ah yes correct. Bab hook and then complete code you can say whatever you have going to a build process but here the catch start. So for an example if I open my laptop or if I open any of the you can say command let's say if I go to I just take any of them I'm just catching it this command And I try that it is a Python program.
I want to run a Python program. So I type py. demo. py. Let's say what is py? I have no idea what is py. Oh sorry. It is Java program. So Java my app dot Java it say what is Java? I do not know Java. What is it means now? Neither in my laptop Python install nor in my laptop Java install. I try to run now build. Ah it's not throwing. Oh it's running. It means that in my laptop I have a net. So what does it means? It means that when we develop a program we develop using a language Java, Python, net.
Let's to understand that we use Java. So all these three developer is my Java developer and in their development everyone have a Java Java Java. Now the build tool say that okay Java which version of Java in which operating system you run the Java code in Windows or Linux. How we can do a build? It has a lot of question now. So it is start asking a question. All right my dear friend which language which OS how to give you build artifact you want in a JIP format you want in a jar format you want in a nut format which format Because remember these tool are just a machine.
It's not a human. In a traditional world, let's say for example this build is managed by I'm just saying Bola. Now Bola going to ask to probably pab. Hey Patab which language? Oh Bulad this is Java. Oh okay okay. Okay okay okay. Which version? Ah Java 10. Okay okay okay. Okay okay okay. Which operating system? Uh I have used Windows operating system. Okay. Okay okay okay. Okay okay okay. How you want to convert the whole program? Just create a jar file, a jip file. But problem is this time it is a tool. How you are going to call a tool?
That is a gocha. So it means that one of the developer it can be Arati it can be spitha it can be a Rajumar one of the developer is not a normal these developers are dev ops developer so let's say Arati know Javas is master in Java But she also master in DevOps development of Java. Vati say all right I am going to provide an instruction to this build tool. It can be a GitHub workflow. It can be an Azure DevOps. It can be a Jenkins. So let's say for example Arati can use YAML or a JSON script.
Arti said all right no worry I am going to develop now an YAML file because Arati has a additional skill other than Spitan Rajumar. She also know how the Deops work. So see write a whole you can say process. Dear build tool must ensure you have a Java 11. Dear build tool please run this command to compile the code. Dear build tool now run this command to test my application. Dear build tool. Now you once you build you package everything in a JIP file. Everything is see written in YAML. So this YAML along with this code go to here merge process it will come to here and then it will finally come here.
So what your build tool do it can be GitHub workflow it can be a job debops it can genkins it will only look it doesn't care about what your code is it will first check that do you have instruction file can be YAML it can be JSON it can be any other format but it should have a so your build say yeah I am going to see your YAML now It all code is here. Everything is here. So along with all the code the build tool also YAML will tool also pull YAML. Now in the YAML in the YAML it say that okay you need a Windows virtual machine or Linux virtual machine.
Oh in YAML it is said that you need a Linux for example it create a VM in the background Linux. Okay your code is written in Java. Okay. Okay. I am going to install a Java. Okay. Okay. Your code is also include a test. You have a test script. I am going to use now JUnit. Oh, to do the build you need a maven. So it is going to now let's say for example it's install maven also and then as per your instruction it run a stage by stage. Okay you told me to first compile your code.
I did. Now you told me to test your code. I run the test script. You told me to create a package. Okay, I created a package. You want me to upload this package to this place? I done that. Whatever you write is go and use. So once the build happen. So when we say build it means that it can be it do a two task. It compile your code and it also create a package. So end of the day it creates something called build. Can I see the build? Yes, you can. Yes, you can. Let's say this is a build.
Who create the build stage? It creates something called build version one. What it contains? It contains Sorry. It contains all your application code. These three it contains when this is copy in the target environment how it run. So there is a special instruction you can say executable instruction file which can be a sales script which can be a power script which can be a simple text script. So any script I mean to say it is now also included in this build. Okay. And now I have a build. So post build it probably go to release.
Who can do a release? Now it can be same three tool and there is a one more tool which is you can people generally use during the release process is encel. enable is very popular release tool where you can release your application packages. So now you have a tools available same question because it's a tool it's not a human let's say for example this relig is managed by a separate person altogether and I'm just taking that it can be Oliver hey Oliver Oliver say because now Oliver is try to automate for it through the release process right so your release tool must want to know okay which package means you have a jar file You have a zip file.
What is the package type? Where to means you want to release it on a cloud. You want to release it on on prem where and how. So they ask a lot of question. Raj Kumar is not a normal developer. He's expert developer debops developer. So most probably Rajkumar may create another YAML file which have clear instruction for the target. Come here. from here from here. Now it sent that YAML file and then this second YAML file let's say also come here this YAML do not read by the build. Let me to just change the this YAML is by release.
So release read the YAML and then release download from wherever you put this build and then it creates something which we can even see it's called release artifact. So let's talk about this GitHub. For a very very long time, use GitHub as a central system. For example, I use GitHub is almost like a 19 years now. 19 years But I see a huge drastic change in GitHub in last four year because when Microsoft is working on its devops tool, Microsoft looking for some kind of a known repository. So they have a choice. They have a choice to use they have a choice to use GitLab they have a choice to use sub version and they choice to use GitHub.
So they understand GitHub is widely accepted and used by most of the developer or you can say people. So they go and acquire the whole GitHub they buy the GitHub. The same GitHub which is freely available to all of us, it is now acquired by Microsoft and it is now have Microsoft brand and same GitHub is available as an Azure your repo in Debop's tool same GitHub. So what the Microsoft does they make the same GitHub available as a private repository in Azure DevOps world. in Azure DevOps world as a Azure repos same functionality everything same but since Microsoft is taken over you know this GitHub this GitHub make lot of enhancement.
They push their developer team to transform this GitHub. So what the GitHub now provide here? The first thing GitHub provide which is known to everyone is a where you can store your all data. They also provide a CI/CD workflow which is called GitHub action. a full project management PMP people use Jiraa instead of a Jira. It give you a full project management with their canban board just like that in you have Azure board. Apart from that, it give you a way to collaborate. Just like a share point you have a collaboration means you can invite team member to join your GitHub.
Apart from that it open its API so that you can connect with your development environment directly to this GitHub. It open now and they make this GitHub availability in a two way. One people like you and me It is a personal or community same community GitHub is now become personal GitHub. No charge free of cost. No charge free of anyone can create an account and that that day be actually create an account and they can also provide an organizational GitHub. In organization GitHub, you have an liberty connect this GitHub with your on premises active directory.
It also give you dedicated GitHub application running in a separate server. So server will not share and then they you have a definitely licensed charge and all this organization GitHub is purely within your company. No one can access from anywhere outside. But no matter are you going to use personal or organization this feature is available across the board like a repo CI/CD action can board you can collaborate you have an API and latest one that is well they introduce use integrated AI tool which is called GitHub co-pilot in a three edition personal professional and enterprise and this is actually a magic same co-pilot now it is integrated inside it of course as a free account you can still use but uh it it has a limitation how many how many type uh time you can ask a question or something but now we have a GitHub uh copilot so this make GitHub is goto tool for a company who probably do not want to go for expensive automation tool like an Azure DevOps.
Yesterday I just say Azure DevOps is a costliest tool. Number one per user license. Number two uh how many time you run a build and release uh in a background it will charge you the compute power also. So for an example if I am a small I want a full CI/CD functionality I want a canon board I want a repository I want a collaboration and I also would probably like to go with the AI I will not go with DevOps because that will going to cost more I can go and use my GitHub I just create an organization account.
I will not pay anything for an example and just use the free account with the limitation of of course but uh I it is good for me. I hope that you understand the power of GitHub in today's context. It also give you an option even in a personal account. You can make it private, you can make it public. in any cases you can use this configuration. For our demo purpose we use it public and then you get an one option called add readme. This is very important when you initialize when you want your repository to be ready the moment you create you should add at least one file by default it add something called readme where you can go and describe your description.
Yeah. And in repository name espita maybe you can type like uh uh MS office ispita orista sorry yeah so that it's recognizable okay now another very important one if you look at below it's a g ignore and this is quite an important one so as a developer as a developer we during the develop time we probably use some of the file where information might be private confidential. I do not want when we push my whole code one specific file should go to a GitHub or maybe a collection of files should go to GitHub. if you want you can add that file in a g ignore.
Git ignore means when you commit everything go except that file. Right now I do not have anything so just leave it blank. And usually when you want put some code some data in a GitHub repository you can also define how this repository can be used by other people. So there are different type of default license agreement available like you have MIT license and so many other licenses right. So, so when we create some very specific code and I want that anyone who want to use my code, they just follow the opensource license agreement. You can pick anyone at this point of time.
I do not want to use anything. So just I say no license. All right. Once you all done hit create repository and please confirm if you are able to see your life. So let us start with the first. So for an example, for an example, let's sayista is project manager. Okay? and you all are team member. So going to now invite all of you as a team member to work collectively on one project and how she will do that. Before that if you look up on little right hand side top there is a one icon it is basically your username last one extreme last.
Yeah click that you see the you have a username please everyone copy this name and paste that name in a chat box. Everyone if you have this name copy this name and paste in the chat box. Okay perfect is now you have multiple name. I think for we are not able to see your name. Yeah lot of people are putting okay very good. Yeah. So what is pitha going to do now? Ispita copy Arati first one. Yeah. Yeah. Put it in a notepad. Put every name name in a notepad. Just copy and put all the name and same everyone you can copy each other name just to see how it work.
Prepare your notepad. Now we are simulating real world environment. Okay. How exactly people collaborate using GitHub if they are going to work on a common project. You can just double click it. Double exactly. This is a login name of your GitHub. Agree. So you should see a login name in your GitHub account. I think Bola has two. Yeah. Okay, that's fine. Now go back to your and look at the process. Make it a full Once you have then in the repository side ah ranger capital. Okay, that's fine. That is just fine. Yeah. Ranger Capital. Yeah.
So, in your repository there is a many menu code, issues, pull request, action, project, wiki, security, insight and last one is a setting. Please everyone go to the setting setting of your repository and on the left hand side just confirm are you able to see under access the first menu is collaborator. Everyone able to see collaborator please click that. Yeah you have to just verify the email properly. Click verify mail. You get a code in your Gmail. Uh yeah, please click that. If it ask for a reverification, please do that. And then you get a option called add people.
Can you all confirm add people? Gregory can you confirm you are able to see add people please click add a people and start pasting name one by one you may get one email in your round. Please find out. You can do it. Ispita, let me go back to Gregory screen. Gregory, can you share your screen and all of you please confirm if you receive ispita email? Yeah. Where is Ah you know what what happened you by mistake do not add which is called uh readme file. So just yeah so if you can create one more so create another repository.
H create new maybe MS office uh Taylor correct like this. And then below you see add readme, right? Just check this box. Uh now click create repository. My bad. Now go to the setting. Settings. Settings. Settings. Just above the just above you have a code. Above code you have a setting. Uh just just little little little left side. Ah exactly. Yes. And then on the left side you have a collaborator first meaning first. Yeah. You have to reverify form. Yeah. Okay. I had to think about the password really quick. Uh okay. Click add people. Patab uh check your speaker.
I think Patab is not able to see or you can rejoin. So now I have to add other one that put their name in the is better. Okay. Okay. Stop sharing. Yeah. So you can add every people and you know you they get a invite. So if when you open email Gri you can see that how the people been invited. Perfectly. Yes. Stop. Yeah. Yes. Please share Go back to all of you. I think that Arati not able to accept or Rajumar accepted. So if you refresh you can see how many people accept your invite.
Refresh the GitHub. Rati, you're not able. Are you able to see the email? Visual check your email and you should able to I think Patab also now created. Yeah, just click uh can you check your also email espita if someone invited you? This is how the invitation email look like. I think no one has uh uh uh Gregory can you add is name? Ispita can you share your name to the chat login name? Anyone of you can you add is pitha in your repository? Just confirm once you add it. Nages added it. Okay. Just check is if you receive any email.
Yeah. Look at that. So ispita now received multiple email from various people who invited. Let's say you click nag email and you get view invitation option. Click view invitation and say accept invitation. Is that clear? How you people can accept invitation to work together, collaborate in a real project world? I think that is I think a lot of people are not accepted your invite as of now. Yeah. Can you accept everyone invite? Uh accept and then you Yeah. Once you accept just close that Okay. Close that tab so that yeah I request all of you to please accept each other invitation just to Yes.
Very good. Now what will happen? Everyone of you please ensure that you should be in the ISPA repository. Can can you confirm uh Patab Rao? I think that he is not. You all can also add my name. This is my name. Please add it. Yes. Ispita refresh and you should able to see IU collaborator. So everyone please can you come to ispitha repository just confirm if you all are able to see ispita repository if you're not able to see again go back and click the view invitation and you should able to see ispita repository. Yes, vigilant.
yeah, very good. Now, everyone please go to the code of ISPA. Everyone come to the code menu. Just confirm if you are in a code menu. Click code menu. Espita. Everyone please confirm you are in a code menu of you get add file option. Click upload file and upload any generic file. This will not be important from your machine. Just upload any file. Okay. So now you you are inspita. Look at that little uh right side below in a third box in a in a sixth box. Is it this one? Look it down. Okay. So once you are there, look at that.
So many people are uploaded. So many file, right? Yeah. all uh this is collaboration. It means that if we all are working on a same project I I use I upload my MS Excel you upload uh probably PowerPoint someone upload maybe MS what right so you can also add a file click add a file add the file where is that okay this one ah and you get upload file any any file from your laptop which is not important you can upload Okay. AJ. Huh? Anyone? Yeah, exactly. Not the folder. You just have to upload a file.
I think AJ 305 draw.io can upload. Okay. This one. Ah, exactly. Upload. Open. So, what? Open. Okay. Open. And in the commit message you just say that uploaded by developer Bola. Oh abab. Okay. Okay. Uploaded by developer bola. You got my developer. Put…
Transcript truncated. Watch the full video for the complete content.
More from Simplilearn
Get daily recaps from
Simplilearn
AI-powered summaries delivered to your inbox. Save hours every week while staying fully informed.









