GitHub Actions の支払いを管理する GitHubは、macOSランナーのホストにMacStadiumを使用しています。
はじめに
This guide explains how to use GitHub Actions to build, test, and deploy an application to Azure App Service.
Azure App Service can run web apps in several languages, but this guide demonstrates deploying an existing Node.js project.
必要な環境
Before creating your GitHub Actions workflow, you will first need to complete the following setup steps:
-
Create an Azure App Service plan.
For example, you can use the Azure CLI to create a new App Service plan:
Shell az appservice plan create \ --resource-group MY_RESOURCE_GROUP \ --name MY_APP_SERVICE_PLAN \ --is-linux
In the command above, replace
MY_RESOURCE_GROUP
with your pre-existing Azure Resource Group, andMY_APP_SERVICE_PLAN
with a new name for the App Service plan.See the Azure documentation for more information on using the Azure CLI:
- For authentication, see "Sign in with Azure CLI".
- If you need to create a new resource group, see "az group."
-
Create a web app.
For example, you can use the Azure CLI to create an Azure App Service web app with a node runtime:
Shell az webapp create \ --name MY_WEBAPP_NAME \ --plan MY_APP_SERVICE_PLAN \ --resource-group MY_RESOURCE_GROUP \ --runtime "node|10.14"
In the command above, replace the parameters with your own values, where
MY_WEBAPP_NAME
is a new name for the web app. -
Configure an Azure publish profile and create an
AZURE_WEBAPP_PUBLISH_PROFILE
secret.Generate your Azure deployment credentials using a publish profile. For more information, see "Generate deployment credentials" in the Azure documentation.
In your GitHub repository, create a secret named
AZURE_WEBAPP_PUBLISH_PROFILE
that contains the contents of the publish profile. For more information on creating secrets, see "Encrypted secrets."
Creating the workflow
Once you've completed the prerequisites, you can proceed with creating the workflow.
The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service.
Ensure that you set AZURE_WEBAPP_NAME
in the workflow env
key to the name of the web app you created.
on:
release:
types: [created]
env:
AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name
AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root
NODE_VERSION: '10.x' # set this to the node version to use
jobs:
build-and-deploy:
name: Build and Deploy
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Use Node.js ${{ env.NODE_VERSION }}
uses: actions/setup-node@v1
with:
node-version: ${{ env.NODE_VERSION }}
- name: npm install, build, and test
run: |
# Build and test the project, then
# deploy to Azure Web App.
npm install
npm run build --if-present
npm run test --if-present
- name: 'Deploy to Azure WebApp'
uses: azure/webapps-deploy@v2
with:
app-name: ${{ env.AZURE_WEBAPP_NAME }}
publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}
package: ${{ env.AZURE_WEBAPP_PACKAGE_PATH }}
Additional resources
The following resources may also be useful:
- For the original starter workflow, see
azure.yml
in the GitHub Actionsstarter-workflows
repository. - The action used to deploy the web app is the official Azure
Azure/webapps-deploy
action. - The "Create a Node.js web app in Azure" quickstart in the Azure web app documentation demonstrates using VS Code with the Azure App Service extension.