Tutorial: Microsoft Azure – Deploying Web Applications Using GitHub Actions

 In this article, we will learn, how to deploy to your web app using GitHub Actions. GitHub Action is a workflow automation utility that has CICD built right in. This means a GitHub user can trigger a workflow run if there’s a new commit, a new pull request, or a new branch is created.

Below is a web app, go into the Deployment Center on the left. And there, you will have options for Azure Repos, GitHub, and Bitbucket.



Now, select GitHub and hit continue. On the screen, you will have a new option for GitHub Actions, so select that.


And now on the next screen, select your repository. Select your username. And then your Spring application that you are going to deploy. It could be any branch, but for example, if you have chosen the master branch. Then, use Java 8 to continue the process. Since you are deploying a Spring Boot application, choose Java SE. If you were deploying a Tomcat application, you could choose one of the Tomcat versions.


So, on the last screen, you have a summary of your selections, so you could go back and edit. And at the bottom, You are looking at a preview of the workflow file that will be committed into your repository. So if you take a quick look, this will run anytime that there’s a push on the master branch. This will check out the master branch of your repo, set up your Java version to Java 8. It’ll build you a Spring app using Maven. And then finally, using the deployment action, it will grab that jar file and then deploy it onto your web app.



So when you click to finish this will start the process to commit it into your repository. Then go into your repo using this link. So, there’s a new directory in your GitHub repo, .github/workflows. So, this is where all of your workflows would be. And if you take a look at the file, it matches the one that was shown in the preview just a minute ago. 

So, what you will do now is come up to the top toolbar, select Actions. And this shows you all of your previous workflow runs and on the left-hand side, it shows you all of your different workflow files.



Now, select one of these workflow files right here. And you can see that that deployment action is running right now.

So if you click that and come over to build and deploy on the left, where you can find all of your different steps of that workflow. And you can even search your logs. So here, we’re looking at the progress of the maven build. And then this is the output of the web apps deploy action. So if you search through some query terms here, you will see that shows up just fine. 



So, moving to the portal. You can see in the dashboard that’s reflected here that the success of the workflow is right there and it’s running.

Let’s browse the application. It’s your Spring Boot app running on your web app and you deployed it with GitHub Actions. 


Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more