Running Java CI pipeline

A free video tutorial from Houssem Dellai
Engineer at Microsoft
Rating: 4.4 out of 5Instructor rating
9 courses
122,505 students
Running Java CI pipeline

Learn more from the full course

Learn Azure DevOps CI/CD pipelines

Create CI/CD pipelines for Java, .NET, NodeJs, Docker, Terraform, Nuget, Xamarin, SQL Server and ARM templates

12:54:45 of on-demand video • Updated September 2022

What is DevOps and CI/CD
Creating CI/CD pipelines for Web, Mobile and Container apps
Including the Database into the pipelines
Configure deployment to Azure Cloud
Run unit, functional and load tests as part of the pipeline
Analyse source code using Sonar
Use Infrastructure as Code (IaC) from CI/CD with ARM templates
Use Configuration as Code (CaC) in Azure DevOps
Create Dev-Test-Prod environments
Secure the pipelines sensitive data
Use Infrastructure as Code (IaC) from CI/CD with Terraform
English [Auto]
Now we are ready to run this pipeline. So let's do that. I go to save. And you hit save. And you. And here Azure DevOps would give me this link in order to follow the execution of my CIA pipeline. So I'll open it in a new window. And here I can see in real time the execution of the pipeline. So now I have found a nation to run my pipeline. It will start by checking out the code from my GitHub repository. So for that we see here some command lines that uses Git. So this one was blown the application and my application source good from GitHub and to the um. And to the agent. Then we were on the maven, uh, clean package command in order to generate the file around the integration test, then publish those integration tests and assure that it will run good analyses or a good coverage in order to, uh, to have, uh, the percentage of the, a good coverage for my application. And now might see a pipeline to Iran in just one minute and 23 seconds. And now all the all the tasks have run successfully. If I go to the summary window from here, I can see the result of the execution of this pipeline. So I can see that it has generated the artifacts. Here we have two artifacts. The first one is for the good cover. So if I go to view the content, I can see that here I have some achievement. And as these files, those will give me a summary of the good coverage for my application. My second artifact is the drop folder and this is the one I need for my c d pipeline which will contain the AJA file for my application. And here we have if we expand the good governance tool here, we can see that we have a good coverage of 100%. That's the result of the analyses done by Jake. If you expand this 60 test menu here, we can see that we have 100% of the tests succeed. Here I have one test that passes. And then there is me and my build pipeline did run it successfully.