-
Notifications
You must be signed in to change notification settings - Fork 0
46 lines (44 loc) · 1.72 KB
/
int-azswa-yellow-sand-079050310.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
name: Deploy Azure SWA (int)
on:
push:
branches:
- int
jobs:
build_and_deploy_job:
if: github.event_name == 'push'
runs-on: ubuntu-latest
environment:
name: int
url: https://int.jimm.my
name: Build and Deploy (int)
steps:
- name: Checkout
uses: actions/checkout@v4
with:
submodules: true
lfs: false
- name: Setup Node v18
uses: actions/setup-node@v4
with:
node-version: 18
- name: Install Dependencies
run: npm ci
- name: Build SWA
run: npm run build
- name: Deploy (skip build)
id: builddeploy
uses: Azure/static-web-apps-deploy@v1
with:
azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN_YELLOW_SAND_079050310 }}
repo_token: ${{ secrets.GITHUB_TOKEN }} # Used for Github integrations (i.e. PR comments)
action: "upload"
###### Repository/Build Configurations - These values can be configured to match your app requirements. ######
# For more information regarding Static Web App workflow configurations, please visit: https://aka.ms/swaworkflowconfig
app_location: "build" # App source code path
api_location: "" # Api source code path - optional
###### End of Repository/Build Configurations ######
###### WORKAROUND Node 18 unsupported by Oryx: Build separately using NodeTool@0 and Npm@1; skip build & use external build in Azure SWA Deploy ######
skip_api_build: true
skip_app_build: true
is_static_export: true
###### End of WORKAROUND Node 18 unsupported by Oryx ######