You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
steps:
- name: Print the user who triggered the workflow
run: echo "This workflow was triggered by ${{ github.actor }}"
- name: Code Checkout
uses: actions/checkout@v3
- name: Node.js Setup
uses: actions/setup-node@v3
with:
node-version: ${{matrix.node-version}}
- name: Clear npm cache
run: |
rm -rf node_modules
npm cache clean --force
npm un -g typescript
npm i -g typescript@latest
- name: 'Resolve Project Dependencies Using Npm'
run: |
pushd './${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}'
npm install
npm run build --if-present
npm run test --if-present
popd
- name: Upload to Azure Functions
uses: azure/[email protected]
with:
app-name: ${{vars.FLEX_APP_NAME}}
publish-profile: ${{secrets.FLEX_APP_PUBLISH_PROFILE}}
package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}
remote-build: true
sku: flexconsumption
tried so many solutions like deleting node modules, granting execution permissions to ./node_modules/typescript/bin/tsc etc, appreciate your support on this and please check the workflow file as well and let me know if we are missing something or going somewhere wrong.
thanks.
The text was updated successfully, but these errors were encountered:
Hi,
Im deploying a node.js backend using github actions to azure functions flex consumption plan and getting the below error,
workflow is as below<
name: FlexConsumption test - Manual
on:
workflow_dispatch:
defaults:
run:
shell: bash --noprofile --norc -exo pipefail {0}
env:
AZURE_FUNCTIONAPP_PACKAGE_PATH: '.'
jobs:
deploy:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [20.x]
tried so many solutions like deleting node modules, granting execution permissions to ./node_modules/typescript/bin/tsc etc, appreciate your support on this and please check the workflow file as well and let me know if we are missing something or going somewhere wrong.
thanks.
The text was updated successfully, but these errors were encountered: