DevOps Full Course 2026 | DevOps Tutorial For Beginners | DevOps Training Course | Simplilearn

Key Takeaways

[Music] Are you looking for a career that's fast growing, high paying, and always in demand? Welcome to the world of DevOps. With companies worldwide moving toward cloud adoption and automation, the demand for DevOp professionals has skyrocketed. Businesses need experts who can streamline software development, speed up delivery, and ensure systems are secure and scalable. And that's exactly where DevOps comes in. So in this course, we'll start from the basics making it perfect for beginners. You'll explore DevOps fundamentals and then dive into powerful tools and concept that are shaping the industry. Here's what we'll cover in the video. First, we'll go through a DevOps tutorial for beginners, a solid foundation, and understand how DevOp bridges the gap between development and operations. We'll have a look at Kubernetes architecture, learn how container orchestration works at a scale. We'll also compare between Kubernetes and Docker. You'll discover the key differences and when to use each. Genkins where you can automate your CI/CD pipelines like a pro. And at last, we'll see top 10 DevOps project. You work on hands-on project to build real world skills. Plus, we'll also prepare you with the most asked questions to boost your confidence for job roles. And by the end of this course, you won't just know DevOps. You'll be ready to apply it, crack interviews, and take on exciting roles in tech companies worldwide. Now, before we move on, here's a quick information. If you are looking to futureproof your tech career, this professional certificate program in cloud computing and DevOps by ENICT Academy, IT Goarti is the perfect choice for you. In just 8 months, you get hands-on expertise across AWS, Azure, Google Cloud, Master DevOps tools like Genkins, Docker, Kubernetes, and work on 30 plus real world projects. And what makes this program stand out? Well, you'll get official Azour certification, IIT Goa credentials, access to life master classes, and even a campus immersion opportunity. So whether you're upskilling or making a career switch, this program offers everything you need to know to thrive in the world of DevOps and cloud with IIT backed credibility and practical learning that actually sticks. So what are you waiting for? Hurry up and enroll now and you can find the course link below. >> Today we're going to go through a complete end to end journey on what it takes to set up a DevOps team. Uh we're going to go through what um we need to be able to do to go to DevOps, what the arguments are and why you need to do DevOps. And then we'll actually go through all the individual tools you need to be able to successfully implement DevOps within your organization. In addition to that, we're also going to take time and go through each of those tools so you get a good understanding of a step-by-step instructions on how to do basic setup of each of those tools. So let's get started. So what was DevOps before? So what was the process that we took for doing delivery before DevOps? Well, it was a model called waterfall. And waterfall was a very traditional approach to actually building out solutions. And the reason why it's called waterfall is that you break out all the individual requirements and individual sections of a project and they cascade off each other. So if we look at the breakdown we have requirements design uh we have implementation we have verification we have maintenance you'll have user acceptance testing and this is all based on the software development uh life cycle model or SDLC and it's been around for quite some time and is still used by a lot of companies today. The challenge you had with the waterfall model is that it really is a very long drawn out model for actually building and delivering solutions. So it took a very long time to actually um write code and then deploy the code. It was very difficult to actually identify problems within the code and provide feedback to the development team on what to fix. Um and this really was a very time consuming. We're talking about months sometimes years for projects to actually go through a warful model process. So along came a new method of being able to do delivery and it's called agile. And the agile approach is a way of being able to take the actual work that's done in a waterfall model and compress it down into small iterations. And what we would do is a fundamental change is that you would actually take uh teams that would disparit and as part of the individual cascades within a waterfall project and you actually bring them together. So you have your requirements team person, a design developer and release management team all together in one group working on an iteration. The great thing about agile is that you took a process that was weeks or months or even years in length as it was with waterfall and you reduce it down to two or four week sprints uh depending on the cadence for your team. Uh typically you have a two-eek sprint and then the goal is is that at the end of uh each sprint or sometimes every other sprint you would do a software release and so that customers were getting the software much faster. The problem that we still ran into though with um agile is fundamentally similar to what we were having with waterfall. uh you have your DevOps person working on code on their system and it' be working great on their computer and then you have the operations person who's migrating the code from the developers environment, the test environment to the production environment and you would run into issues where the code simply wasn't work and there's a lot of reasons why that would happen. Uh the actual developer environment would often be very different or would have different dependencies in it. So the uh the hardware, the the software, there may be additional uh applications that were installed on the operating system that simply hadn't been transferred over to the operations environment. And so what you would have is a disconnect between the developer environment and the operations environment, making it difficult um to actually roll out code. So you'd run into a program where that when you rolled out code, you'd have to have a roll back plan in case the code wouldn't work in production. And so each release became an event where everybody got very stressed about the actual event of releasing code because you didn't know whether it was going to work. So Dev Ops really looks to address and solve a lot of these problems. So the key word that you'll often hear with uh DevOps is continuous integration. And what that means is essentially that as a developer is working on their code, their code is constantly being tested against not just the actual code itself with unit testing, but the environment with which it's going to be released in. And the goal from a dev ops model is that the breakdown of communication that happens with waterfall and agile where dev developers and operations teams aren't working in the same environment is being removed and you're able to provide a continuous and contiguous um environment uh between the developer and the actual operating model. So the reality is when the developer is working on their code, they're actually working in an environment that is identical to the production environment. And so when the actual operations person comes to actually do releases for the code and you can see some teams are doing as many as 20 to even up to 50 releases to production environments every single day. you're able to guarantee that the actual code itself will work and releases go from being a stressful event to a byproduct of good testing and good setup and structure for how you actually build out your solutions. So what we're seeing here so the goal is that as a developer and as an operations person that the code is working continuously in both environments. You have continuous integration and continuous delivery. So simply put, what we're able to do is we're able to eliminate the problem of the operation environment not being in sync with the development environment. And this is a an improvement on agile. This is not to say that waterfall or agile are wrong as delivery models. What it is is just a maturity of the ability to deliver solutions and DevOps is just another rung in that maturity curve using tools that are available to us now that 5 10 years ago simply weren't available. So the goal is for you as a team to move to a dev ops model where you can implement continuous releases on your software as long as you're using the tools that are available. And the good news is those tools are open-source tools. So let's go through some of the benefits of why you'd want to go um and use DevOps. So you know essentially what's in it for you. So let's over the next few slides we're going to go through what is DevOps. We're going to go through the benefits of DevOps. So in the last few slides you've actually seen you know what is DevOps and the benefits of DevOps along with the life cycle. But we're also going to start digging into the tools that you have that are useful for DevOps. And we're going to focus in on seven tools that can provide an end-to-end infrastructure for delivering DevOps solutions with there are significantly more tools available on the market. Uh but these are seven of the most popular uh for each of their categories. So DevOps really is an essential collaboration between the development team and the operations team. These are teams that have in past been somewhat at conflict with each other. And what you have now is an opportunity where those teams can can now work continuously with each other. The expectation with DevOps is that it will continue to mature. Indeed, you're actually even seeing some groups which are now called dev sec ops where they're integrating security as part of the delivery between the development team and the operations team. The bottom line is a DevOps engineer is highly in demand. The demand for a DevOps engineer is literally going through the roof with salaries going up exponentially around that. So let's dig into some of the benefits of DevOps. It's not just a new catchphrase. It's actually got significant value and how you can speed up delivery of your software. So the benefits of DevOps can really broken up into a number of key areas. First of all, we have continuous delivery of software which allows you to continuously release new features with the security and understanding that the software going out is of high quality. It allows the teams that are working on the software delivery within your organization to more effectively collaborate with each other so that you're all talking from the same page and understanding of what needs to be delivered. The deployment process itself moves from being an event where there's a lot of stress and there's a lot of contingency plans to being a much easier deployment. The efficiency within the actual code that you're writing and the ability to scale up using the different tools are available allows you to be able to bring in and scale up and reduce the teams you have running the software as needed. errors can be fixed much earlier and more quickly and can be caught before anything gets pushed out to the production environment. And fundamentally what we're looking for is improving the security of the actual releases. So the actual concept of security is center to all the work you're doing. And then finally what really allows you to reduce the number of errors is that there is much less manual intervention. there is a greater reliance on scripted environments that you can actually test and validate for their security, reliability and uptime efficiency. So let's talk a little bit about the life cycle of a devops. So the very first step that you'll take is to actually build out a build and test environment. And this is a continuous build and test environment. And this is managed with the first step of your source code. Once you move through that and you're looking at continuous integration, which means that every time somebody checks in their code, they're validating that the code actually can run in the production environment. Once you've actually then passed the continuous integration and the testing that you have with your code, you're looking at continuous deployment. If the code works and is available to be released into the production environment, let's go ahead and release it. And once you actually have release code, then you want to be able to validate that your environment is working efficiently. You may release code that is a new feature within your application and customers may then gravitate immediately to that new feature. If they do, you want to be able to ensure that the code is working and more importantly that the infrastructure is there to support. And then finally, you're looking at software released um as a continuous event. And then you go back to the beginning. You start working on more code. You run it through your build environment and continuous integration, deployment, continuous monitoring, and keep that cycle moving. So let's dig into the tools that you as a DevOps engineer would need to learn. If we break down the environment that we have all the way from source code management to software release, there are a number of key tools that you want to be able to use. So for instance, source code management git is an open-source tool that you would want to use for managing your code. The continuous build and test environment would be managed with Maven and Selenium. Integration with the environments that you're working on is managed through Jenkins. The actual deployment to your production environment would be managed with products such as Anible and Docker. And then the monitoring of your network would be used with tools like Negios. The thing that you have to remember with all these tools is that they're open-source tools. There is no licensing that you have to uh purchase. Uh some of the tools will have prolevel licensing that you can choose um to select. But to get started, all of these are open- source tools you can actually start using for free right now. So let's dig into Git. So let's look at the the challenge that Git is able to address. So before git and you if you had a team of developers that were working on different pieces of code, one of the key problems you have is that there was no collaboration between the team. And the the challenge you have is that with version control it was difficult and often required um having to check in to a large environment or you had very you know quasi version control environments. It was time consuming. Often there were problems that what would happen if this the uh version control server would crash and there wasn't a backup then you'd have to kind of essentially go back to square zero uh to see whether or not you actually had to do the work again. So let's look at what git does to actually solve this. So first of all one of the things that um git does is it makes team collaboration much easier. The software itself is more effectively documented and more and more effectively maintained. the actual code that actually gets worked on by each developer in a git environment is the complete code. So it makes it much easier for backups and for sharing uh content amongst each um developer. So the way in which git is able to accomplish this is that it is essentially a distributed version control um solution. Um, and what that means is that when you have multiple developers, yes, you do have a git remote hub that you connect and uh are able to upload and download uh different branches of the code that you're working on. But essentially as a developer when you um actually have the code, you actually have all of the code and uh you're able to uh manage it directly from your local PC or your local development machine um without having to uh worry too much about the network or the server actually going down. So some of the key things in which um git is really good at it is you know a software management tool. It's designed from the ground up to manage code development. It does track the changes on that code easily and effectively. It makes it easy for you as a developer to track your code. The ability for multiple developers to work together is much easier in comparison to um other solutions. And and this is really the the key success point with Git is that it allows for nonlinear code development. So you can actually have people working on different areas of the code that may be released at different times because of what they're working on. So if we actually break down the architecture of git, it really falls into four key areas of a working directory, a local staging area, a local repository and a remote repository. So the process you would go through is you would add files to this um staging area from your working directory and this would be use the get add command and then from your staging area when you're ready to actually then commit those files to a local repository you would use the get commit command. And then from there you would actually then push your local repository out to the remote repository uh for a final commit uh to the remote repository. Um and this allows then the rest of the team to pull down your latest final changes. So you can be working on your code locally and you can be using your local local staging area, local repository and and when you're ready to commit your work, you can commit it and then as soon as it's committed, the rest of the team can then pull down the latest changes that you have worked on. And this allows for a complete and holistic checkout and checkin process. And then sometimes you want to be able to go through and then take the checked out code that you um that you're pulling out and merge it with your local code. And the merge process always ensures that uh you are working on the latest and best version of the code and everybody on the team is being consistent with the uh communication of the actual code that's being delivered. Okay. So what we're going to do is we're going to validate that we have git running on our computer. We're going to then create a directory, add a file to that directory, make some changes to that file, and then use the commit commands to be able to check in the files and validate changes that have been made. So, first thing we do is we're going to see if we have git um installed. And to do that, you just use the command git version and what you'll sorry, git- version. And that'll actually then give you the version number. And now we're going to create a new folder. So, mk dur green. And that'll create a new folder. and we'll move our cursor into the green folder by changing the directory. And we can go back into Windows and we can validate that that directory is actually there. So here we go. Let's have a look. We should see it. There's the green folder. If I double click into that, you'll see there's nothing in the folder right now. So what we have to do is we actually have to add the folder as part of a git project. And so we're going to use our git initiate in it. And that will actually initialize the folder and make it a git repository. And so let's go ahead and create a file that'll actually go inside of um that uh new initialized folder. And you'll see that there's a git folder that's been added. So the new text file we're going to create is going to be called class. And it'll actually be class.txt. The extension is hidden by default. In the uh text file, we're just going to type in the text welcome to simply learn and save that. Now let's go ahead and check the status um of that file in git. So let's do get status and you'll see that it says yes there's a file there but it hasn't been committed to the repository that's why it's in red. So what we have to do now is commit the file to the repository and it won't be able to track any changes that we do to that file. So let's go ahead and commit the file. So we do commit add class txt and they'll add that to the repository. And there we are. It's added. And the final step is we want to do is commit it. Let's do get. So let's do get commit-m put in this will be our first commit and this is the description and so it actually shows us committing the file. It's the only item in the folder. So now we can go over to the file that we just created and we can make some changes to it. So let's open up the file. So it says welcome to simply learn. Uh let's put in some text afterwards that says this is my demo. And we'll save that. Close that. And now if we go back to git, we can do a compare and contrast between the original file that we committed and the new um updates that we've just done. And we can check the difference by using git diff. And what you'll see is the uh red text was the original text and the green text is now the new text that's been added. And so that shows you how you can actually go and create a um a new git repository, go through adding files, committing the files into the repository, and being able to see the different version controls. Let's move on to Maven. So why use Maven? So, so why use Maven? Well, let's look at some of the things that you would have done in the past if you actually building out the tasks. So let's break down what you would have done before using Maven. If you were to create a game of football using Java, you'd actually have to go out and for your actual um game, you'd have to collect all the different components needed within the Java environment uh to make sure that everything would work correctly. And if you make the slightest mistake, uh you wouldn't get the right output that you needed. The actual process of building and deploying a project really would take quite a lot of time. After Maven, Maven allows you to be able to take templates that are stored locally and be able to use those to be able to improve the efficiency of being able to build out your environment by removing dependencies within the application. It makes it a lot easier for you to be able to focus on just writing the code for your game or your solution rather than having to manage the environment within which that solution would be deployed. Now the focus within Maven is that it is an automation tool and it's used for projects that have a short period of time. So as you're starting on your environment for building out um solutions, Maven is great to get started with and then if you need to have longerterm projects then you can look at other alternative tools on the market. So, four key areas that you want to focus on and why Maven can help you is that it does allow for efficient um parallel builds to be run concurrently. It's really easy to use. You can get up and started with Maven very quickly. Uh you do have fast access to new features and new configurations quickly within your environment and the build process that allow you to be able to visualize your code happens very quickly. The actual architecture of Maven is that the execution and commands are managed through what's known as a pom file. The pom file itself is a project object model and it's an XML file that actually has the details for the project and the configuration for the build environment. Pom file itself will then fetch dependencies from the local repository and will apply any plugins that you may have also included within your Maven environment. The goal is that your software is built much more controlled manner. So what we're going to do now is we're going to show you how to go through and run your very first project using Maven. The first steps you're going to have to do is make sure that you have the latest JDK installed on your computer. So we're going to go ahead and open up our web browser and get this installed on your computer. So, we're going to type in JDK download into our Chrome web browser and go to the Oracle website, which allows us to download the JDK. And because we're running this on Windows, we're going to download the Windows version of the JDK. And once you have that installed, so the next step is to actually then go ahead and download the Maven files. So, it's going to take us to the mavenapache.org org website where you can actually go ahead and download the version of Maven that you need for your operating system. We're going to go ahead and download the zip file instead of just an executable file. This will give you more control over how you install it onto your Windows PC. After the file has been downloaded, we want to go ahead and extract the entire um file so you have uh the unzipped folder running on your computer. So, one of the things that we're going to have to do is go through and set a number of system variables for the JDK and for the path to your Maven files. And to do that, you want to go into your control panel and select the system security and then system settings and then go into advanced system settings. This will give you access to the uh edit system variable setting that you're looking for. So, we're going to go down to the path variable, and you'll see already that we have pasted in the link to the JDK uh right there underneath the variable value. If you've installed the JDK, it's likely that it's already installed this path for you correctly. The good news is it's actually fairly easy to uh install the path to Maven and to the JDK because all you have to do is copy the path for where the folder is located on your system and just paste it into a variable value under the edit systems variable fold um file system. And that should now get us all the files. And you can see that we have our extracted folder already on our desktop there. And the system path is now um set to where the Maven folder is located. So we also have to go into system protection and set the system path to your Maven folder. Now we have to go ahead and do a user variable that also part links to the path of the Maven files. So what we're doing right now is we're just validating that all the files have been extracted correctly. They have which is good. We can now go ahead and link to this moment folder. All right. So now what we're going to do is we're going to move over to command prompt. This is where we're going to do most of our work from here on out. First command we're going to do is uh mv. So we're going to go ahead and create a new user variable and uh we're going to type in we're going to call this one m2 dash and then we'll put in the path uh to the Apache Maven folder. You should be able to use m2-home uh for your project, but if it's not, you can always use the variable name maven-home and that will do exactly the same as uh m2. We're going to do both here uh just so we have a backup. So, we're going to open up command prompt and we're going to see if Maven is installed. We do that by writing mvn- version. And here we are. Yes. So now we're going to go ahead and create our first Maven project. And the first part of creating the Maven project is actually the directory in which we will store the files that will be used to create for our project. So we're just going to go ahead into the folder and we're going to create a new directory and we're going to call this one and we're going to call it simply learn. And we can just copy the path for that. So I'm going to write this the uh correct path for us. So we're going to change directory CD and copy the file location over. All right, we are now moved ourselves over to the simply learn folder and we'll be able to install the pom file which is what all the instructions for Maven are stored in uh into this area. So to do that, we're actually going to use a template that's already been created by Maven. And this is going to be the MVN archetype template. And so you just do mvm archetype colon generate and this will go ahead and create all the files for us. So there can be quite a few files and they're all being downloaded from the Maven website. Uh so it can take some time but as you see we've gone ahead and all the files have downloaded and we have everything up and running correctly inside of our environment on command line and command prompt. So we'll have some values that we do have to set. The first one is group ID and we're going to call this one com.mav. And then the next one is going to be artifact ID and this is going to be mav mav- project. Hit return. And then version is going to be 1.0- snapshot. We'll just put in the same value for this version be 1.0- snapshot. And the package we're going to type call this one com.mnav.demo. And then we'll select yes or w toh create the environment and it will build the environment for us. And what we have now is we have this screen which shows everything is up and running for us. And we have a successful build. And so let's go into the maven folder and just see there we have our simply folder. Let's open up and see what's in there. So we double click into that directory. Yep. And there we are starting to see some of our files. So, it's um the same project names there as mav- project. And then we have our pom file that's in there, which is fantastic. Under the source folder, we'll actually see the uh the demo and we have our app under the demo app. We have our test file as well. So, in the main folder, we have a file that's called the pom file. And that really is the most important file that you need for your project. You'll now go in, you'll be able to set all your settings inside of that pong file. But that's it. That's what we have done here is we've gone through and we've gone through all the setup that allows you to uh make sure you have the right files running on your computer, the right files to download from the Maven website, how to install all the files, the settings you need to make on your Windows computer, and then all the settings that need to be done in the command line to be able to run the application. And then from here you can actually start running Maven. Now let's look at selenium as we get start looking at testing. So before selenium if you wanted to run testing and particularly if you wanted to do sequential testing it would take up a lot of time. You'd have to run one test then the second test and then all the other tests and the actual time elapse would be quite significant. With selenium you're actually able to do parallel testing. So instead of looking at the amount of time it would take to actually run a test and run the test sequentially, the length of time to actually run your test is based on the length of the longest running test of which in this example uh the longest running test is 2 minutes. Now one of the things that you'll notice with Selenium is that its focus is on web applications. Um, and it is an open-source tool and it's really good at regression and functional testing of web applications. If you're doing a mobile application or if you're doing an IoT application, there are other uh tools you can use on the market as well. But if you are new to DevOps and you're setting up your first DevOps environment, Selenium is a great place to start. And web applications are mature and allow you to be able to test out and validate the concept of continuous testing in your environment. So, four key takeaways uh for Selenium. Um, it really is fast. I mean, for fast execution, it's highly accurate. Um, so you can always validate that what you're doing uh will work correctly and feedback can be sent straight back to the developer if their uh code doesn't pass the test. Um, allows you to script in multiple languages. Um, again, this is a great way for you to test. The focus is on web applications, but you can um test in multiple languages used for web applications and most importantly allows for parallel test execution which speeds up the whole test process significantly. Actually to break down the architecture of Selenium and what you'll find is the actual libraries that you can use for Selenium run in uh C, Java, Python, JavaScript, PHP. Uh these are the common languages used to build out web applications. The actual web driver itself is an API driver um which is fantastic because it makes it easier for you to integrate Selenium with applications through API and you can run the solution through different web browsers. The most popular being Firefox, Chrome and Edge. So to focus, the Selenium web driver codes are being used to build out the client libraries that make it um to allow you to be able to build solutions across multiple web um application environments. The web driver application interface is used to integrate with the application to make it easy for testing. The web driver service provides an immutable stateless environment that makes it very easy for you to be able to use protocols such as JSON to wire up your test environment. The driver manages communication between the browsers and the wire protocol that's used for JSON within the web browser itself. And then the actual commands are then run through the web browser for you to be able to get your results. Okay. So before we actually get into the setup of Selenium, the first things we want to do is we want to make sure that we have the right version of Java installed. And so I'm just using command window here and I'm going to type in Java. And actually what I can see now is I do have Java installed, which is fantastic. Otherwise, you'd have to go and download Java from Oracle's website. The next step is to validate that I have Eclipse installed. And I'm just typing Eclipse. And there we are. I have the Eclipse app installed. Uh you can actually download um Eclipse from the Eclipse website. The third step I want to check is to validate that I have a browser driver installed. So I'm using uh Google's Chrome um for my main browser, but you can actually go out and download the Chromium driver um and that's the actual core engine that powers Chrome. Uh interesting enough being used in the new Microsoft Edge web browser. So you can actually go and download the latest uh Chromium driver and install that. And then the final stage is to go to the Selenium website and download the JAR files themselves. So just uh do a Google search on Selenium download. And here we have the Seleniumhq.org website and it takes us straight to the download page. And we want to download the latest version. And we've gone ahead and done that already. So we have everything running. And now the next step is for us to install all of this great content. Okay, so before we actually get into the setup of Selenium, the first things we want to do is we want to make sure that we have the right version of Java installed. And so I'm just using command window here and I'm going to type in Java. And actually what I can see now is I do have Java installed, which is fantastic. Otherwise, you'd have to go and download Java from Oracle's website. The next step is to validate that I have Eclipse installed. And I'm just typing Eclipse. And there we are. I have the Eclipse app installed. You can actually download um Eclipse um from the Eclipse website. The third step I want to check is to validate that I have a browser driver installed. So I'm using uh Google's Chrome for my main browser, but you can actually go out and download the Chromium driver. Um and that's the actual core engine that powers Chrome. interesting enough being used in the new Microsoft Edge web browser. So you can actually go and download the latest uh Chromium driver and install that. And then the final stage is to go to the Selenium website and download the JAR files themselves. So just uh do a Google search on Selenium download and here we have the seleniumhq.org or website and it takes us straight to the download page and we want to download the latest version and we've gone ahead and done that already. So, we have everything running and now the next step is for us to install all of this great content. So, we're just going to go ahead and open up the Eclipse environment. And it always takes a moment to launch Eclipse. And we're going to go ahead and create a new project. And we're going to call our project XYZ. I think that should be fine. And this is just a test after all. And we're going to go ahead and create a new class file by right-clicking and select new class. And we're going to go in here and we're going to give the class file a name of simply learn. And don't see the finish button being selected. So maybe we need to select some other options here. Oh, you know, I think it could be the package name. Yeah, let me go ahead and change the package name. And I'm going to change that to QWE. QW app. Yep. And the finish button has now been highlighted. I can select that. I can go select that and click finish. And uh we now have a test page that's up and running. But what we have to do is to validate that Selenium is actually part of the project. So to do that, we're going to go to the source to the actual source XYZ file and right click on it. And we want to validate that all the files are there correctly. And so we're going to see that we have the libraries are there. Yep, there's Selenium. If it's not there, you can select add external files and find the Selenium Java file. Select open and that would load that in there. And then you hit apply and close and that would apply it to your project. And now we can actually start writing the code part. So we're going to put this uh code in the public static void section. And the first uh command is going to be a system setpropy. And we want to make sure that we're configuring the web driver for Chromium correctly. So we're going to do web driver um chrome driver. And then the argument is actually going to be the full path, full network path to the Chromium driver that you have on your PC. So let's see, we have Chromium here. We want to copy that path. And so that paste that in. And then after we've pasted in the path, we have to make sure that we also put a link to the actual file that we want to execute, which is in this case is chromedriver.exe. And then we want to make sure that the web driver is pointing to the new chromedriver. And you'll notice that there's a couple of red colors on here, which means that we don't have all of the public classes imported correctly. So you can right click on that and say import the web driver and just select that real quick. And that adds the import correctly at the top of the page. And same for Chrome driver. And that's just a very quick way um when you're working in Eclipse to import additional uh files. So before we actually start our test, we want to make sure that we've actually cleared out any potential browser cookies that would be within the Chromium driver. So for that, we're actually going to go ahead and we're going to write a script that allows us to remove the cookies. So we want to do driver.mage and then delete all cookies. And the next line we're going to do is to actually have the web page that we're going to connect to open up in full screen mode. And for that to happen, we're going to go and actually use the window property, which is what I was writing before by mistake. And so this will allow us to go full screen. And now we need to pull in a web page. So we're going to get the get command. And what we're going to do is we're actually just going to pull in a web page from Amazon. Uh which I just happen to have here. So I'm just going to go to Amazon web page. And so I'm just going to copy the URL. Uh you know, just need to copy https uh www.amazon.in or.com wherever you're located. And so you can see that I've pulled in the Amazon web page. And then line 18 actually allows me to go and connect. So here we are. we have uh the Amazon web page that I'm pulling in. And then what I also want to do is I want to look for a specific ID in one of the elements and so I have the uh driver which is called find an element and that allows me to look for any element that would be on the actual page. So here we have the HTML in the console screen and I can actually then paste out an ID from the element that I want to use. So the find element is just the ID for each element and most of them have them because they need it for the JavaScript and CSS. So let's see there's quite a few IDs. So and we can select any of those. So what we have here is we have two tab search text box and then what that actually does is that finds the ID for the text box used for searching and then we're going to use the send key command which allows us to actually prefill in the search box and we're going to use the test of Puma shoes. This is a fixed string but you could actually put a variable in here if you want to pull strings from a database or an XML file. And then the next uh line on line 19 which shows how long we're actually going to run the actual script for the uh search which is only 10 seconds. And then once the uh 10 seconds has elapsed, we'll actually quit the script which actually closes the web browser and takes us back into our screen here. And let's test that. Make sure it's working and everything's looking good. The web browser opens, which is what we expect. It goes to Amazon. Fantastic. Um, it now actually goes to the search screen and should fill in the Puma shoes. There we go. Puma shoes. And waits 10 seconds. And it closes. And that's exactly what we were expecting. Now, you can actually change the unit of time that you would have for the actual test. So, if you wanted to see what was happening, so longer than 10 seconds, you can actually change the actual time or the actual metric. So in in this instance we got it says seconds and unit of time but you could do minutes or hours or microsconds and you can change the keyword as well. So it could be jigsaws or anything you wanted to check. But if you're actually building your own application, you want to be able to test your own data against your own application, that's where you put in that specific data. So let's look at the center the heart of um your DevOps environment and that center is with Jenkins. So before Jenkins people would uh developers would work on their code and the code would then be checked into a source repository. You would then check for any issues and then you would then send that uh code over to the operations team and there would be a delay for actually delivering software. So the actual um uh challenges developers had is that if they wanted to run any tests, they had to wait until their software was built and there was a lot of problems in providing feedback particular if you had large teams working on software who actually had the error. The actual delivery of software was often uh delayed uh because of these key problems. So after Jenkins, what we actually have is the ability to be able to streamline this whole process. The build, test, and deploy happens continuously and are able to then notify developers and the actual specific developer of any errors that are detected. Being able to speed up the delivery process much more efficiently. The focus of Jenkins is that it automates a continuous development, testing, and deployment environment. And it's opensource. Jenkins is easy to install and configure. It's been around for many years now and it is very mature. There are many plugins that you can use within Jenkins to be able to have the Jenkins product work with your environment. If there isn't a plug-in, you can actually extend via you can actually write your own plugins if a plug-in doesn't exist. So, you can actually continue and extend and invest in the Jenkins ecosystem and it can be easily distributed across multiple machines. So let's break out the architecture of Jenkins. So Jenkins starts as a remote source code repository and it then pulls out the code every time there is a commit from into the server master. The server master will then have a slave that will run on either Windows, Linux or Mac OS to be able to distribute its load across those environments. And after it's actually gone through and run its test, it'll then send out a report. The goal of the report is to communicate back to the team what has passed and what has failed the actual check-in process. Okay, so we're going to go ahead and show you how to install Jenkins on your local PC. Uh so the first thing you want to do is check that you have Java installed. So we're just going to go into our system and see whether or not we have the Java JDK installed. You can do that by going into the system properties, secting advanced, and then environment settings. And there we are. We have Java JDK installed. And you want to just double check on the system variables to make sure that you have the Java_Home installed correctly as well. And we have that installed. And under path also make sure you have a link to the uh Java JDK as well. So we have everything installed and what we're going to do is we're going to open up command window and just do a double check right there. So open up command window and we're just going to check that we have Java installed. So we do java dash version and we have a version number that comes back. If we didn't have Java installed, we wouldn't get a Java version number come back. We'd actually have an error. All right. So everything looks good. So the next thing we want to do is to go to the Jenkins website and download the files. So we're going to go to jenkins.io. And that's the official Jenkins website. And if you want to download, you just go to jenkins.io/d io/d download or you can just uh type into your search bar uh download Jenkins and that will give you a link straight to the download page. And one of the things that you'll see is that there's lots of different versions uh for Jenkins because Jenkins runs on pretty much uh most operating systems uh including Windows uh Linux and Mac OS. But we want to select the Windows version. So we've already gone ahead and downloaded a zip file which contains all of the files that we need for Jenkins. And so that's the zip file and we've expanded it. And what we want to do now is h double click the installer file and we'll go ahead and install that. So we've already installed this. So um one of the things that we'll get is a message asking if we want to repair. You would actually get a install message because it' be a fresh install for you. Um, but once you've done that, it has all of the files and all the settings correctly installed onto your Windows computer. And we do all of our commands for Jenkins through um a web page that's run locally on your PC. And so you're going to type in localhost colon 8080. And when you do that, they'll actually take you to Jenkins running locally on your PC. And here we have our Jenkins dashboard. And we've already gone in and created some sample jobs. And you can see those listed on the uh sorry on the right hand side of the screen. So let's go through some of the things you would want to set up here. So first of all let's go into the manage Jenkins screen and that will actually so we'll go to the manage Jenkins tab on the left hand side uh to do some standard configuration settings. So, we're going to the configuration systems and if you want to, if you're like remotely connecting to a remote Jenkins environment, you can actually install a JDK remotely for on that machine if you want to. We already have the JDK environment already set up. So, yeah, that's good here. So, we don't need to do that. But you'll also see as you go through the uh the list of applications that you have, Gradel, Ant, Maven, Docker, uh Git and other tools that you would use in a DevOps environment. Uh there are many other tools you can install through plugins as well. Let's have a look at one more setting here with the security. The default security is Jenkins own user database. Uh that probably is not allowed within your company due to security um restrictions. Um so you can choose LDAP which allows you to connect with your active directory configuration. again because there are so many plugins uh for Jenkins uh there are plugins for SAML authentication as well as OOTH. So let's go ahead and start a new build new build job and so we'll select new item and we're going to select demo one from that create a new item and we're going to use just a freestyle project because I just want to demo how you can actually create a build. Okay, description. Uh gosh, what could we write here? Um, we can put in snippy demo. And we're not going to use source code for this one. We're going to do that in the next demo. But, uh, this what we want to go down to is the job type. And we're going to so build and we can just do um add for wind execute Windows batch command. And so, let's just put in a very simple command. And so, we're going to type in echo open quotes world. And then we'll put in the time stamp. So we'll put in date first and then time as part of our output close quotes and we're going to save that alo sit save and that's our simple project. So what we want to do now is we want to actually go and select the build now command to actually run this project. Build now and it'll take a couple of minutes for it to run. And here we are. This is our project and we can actually now see the different builds that have happened. And if you look on the build history, you'll see the latest history shows uh when the build was executed. And if you click on that uh you can actually start getting information such as the console output will actually provide information that we were asking for. So for instance uh we have it's first of all we can see that the build was successful and we see the output includes uh the hello all and date and time. So, we're going to go ahead and create one more project where we can actually connect to a GitHub and use the git command tool to be able to build a real project. So, we'