Azure AppService deployment node-based build script
@if "%SCM_TRACE_LEVEL%" NEQ "4" @echo off | |
:: ---------------------- | |
:: KUDU Deployment Script | |
:: Version: 1.0.15 | |
:: ---------------------- | |
:: Prerequisites | |
:: ------------- | |
:: Verify node.js installed | |
where node 2>nul >nul | |
IF %ERRORLEVEL% NEQ 0 ( | |
echo Missing node.js executable, please install node.js, if already installed make sure it can be reached from current environment. | |
goto error | |
) | |
:: Setup | |
:: ----- | |
setlocal enabledelayedexpansion | |
SET ARTIFACTS=%~dp0%..\artifacts | |
IF NOT DEFINED DEPLOYMENT_SOURCE ( | |
SET DEPLOYMENT_SOURCE=%~dp0%. | |
) | |
IF NOT DEFINED DEPLOYMENT_TARGET ( | |
SET DEPLOYMENT_TARGET=%ARTIFACTS%\wwwroot | |
) | |
IF NOT DEFINED NEXT_MANIFEST_PATH ( | |
SET NEXT_MANIFEST_PATH=%ARTIFACTS%\manifest | |
IF NOT DEFINED PREVIOUS_MANIFEST_PATH ( | |
SET PREVIOUS_MANIFEST_PATH=%ARTIFACTS%\manifest | |
) | |
) | |
IF NOT DEFINED KUDU_SYNC_CMD ( | |
:: Install kudu sync | |
echo Installing Kudu Sync | |
call npm install kudusync -g --silent | |
IF !ERRORLEVEL! NEQ 0 goto error | |
:: Locally just running "kuduSync" would also work | |
SET KUDU_SYNC_CMD=%appdata%\npm\kuduSync.cmd | |
) | |
goto Deployment | |
:: Utility Functions | |
:: ----------------- | |
:SelectNodeVersion | |
IF DEFINED KUDU_SELECT_NODE_VERSION_CMD ( | |
:: The following are done only on Windows Azure Websites environment | |
call %KUDU_SELECT_NODE_VERSION_CMD% "%DEPLOYMENT_SOURCE%" "%DEPLOYMENT_TARGET%" "%DEPLOYMENT_TEMP%" | |
IF !ERRORLEVEL! NEQ 0 goto error | |
IF EXIST "%DEPLOYMENT_TEMP%\__nodeVersion.tmp" ( | |
SET /p NODE_EXE=<"%DEPLOYMENT_TEMP%\__nodeVersion.tmp" | |
IF !ERRORLEVEL! NEQ 0 goto error | |
) | |
IF EXIST "%DEPLOYMENT_TEMP%\__npmVersion.tmp" ( | |
SET /p NPM_JS_PATH=<"%DEPLOYMENT_TEMP%\__npmVersion.tmp" | |
IF !ERRORLEVEL! NEQ 0 goto error | |
) | |
IF NOT DEFINED NODE_EXE ( | |
SET NODE_EXE=node | |
) | |
SET NPM_CMD="!NODE_EXE!" "!NPM_JS_PATH!" | |
) ELSE ( | |
SET NPM_CMD=npm | |
SET NODE_EXE=node | |
) | |
goto :EOF | |
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: | |
:: Deployment | |
:: ---------- | |
:Deployment | |
echo Handling node.js deployment. | |
:: 1. KuduSync to DEPLOYMENT_TEMP | |
call :ExecuteCmd "%KUDU_SYNC_CMD%" -v 50 -f "%DEPLOYMENT_SOURCE%" -t "%DEPLOYMENT_TEMP%" -n "%NEXT_MANIFEST_PATH%" -p "%PREVIOUS_MANIFEST_PATH%" -i ".git;.hg;.deployment;deploy.cmd" | |
IF !ERRORLEVEL! NEQ 0 goto error | |
:: 2. Select node version | |
call :SelectNodeVersion | |
:: 3. Install npm packages | |
IF EXIST "%DEPLOYMENT_TEMP%\package.json" ( | |
pushd "%DEPLOYMENT_TEMP%" | |
call :ExecuteCmd !NPM_CMD! install | |
IF !ERRORLEVEL! NEQ 0 goto error | |
popd | |
) | |
:: 4. Build the website | |
IF EXIST "%DEPLOYMENT_TEMP%\scripts\build.js" ( | |
pushd "%DEPLOYMENT_TEMP%" | |
echo "Building web site" | |
call npm run build | |
if !ERRORLEVEL! NEQ 0 goto error | |
popd | |
) | |
:: 5. KuduSync to DEPLOYMENT_TARGET | |
echo "Syncing site to Deployment Target" | |
call :ExecuteCmd "%KUDU_SYNC_CMD%" -v 50 -f "%DEPLOYMENT_TEMP%\build" -t "%DEPLOYMENT_TARGET%" -x true -i ".git;.hg;.deployment;deploy.cmd" | |
IF !ERRORLEVEL! NEQ 0 goto error | |
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: | |
goto end | |
:: Execute command routine that will echo out when error | |
:ExecuteCmd | |
setlocal | |
set _CMD_=%* | |
call %_CMD_% | |
if "%ERRORLEVEL%" NEQ "0" echo Failed exitCode=%ERRORLEVEL%, command=%_CMD_% | |
exit /b %ERRORLEVEL% | |
:error | |
endlocal | |
echo An error has occurred during web site deployment. | |
call :exitSetErrorLevel | |
call :exitFromFunction 2>nul | |
:exitSetErrorLevel | |
exit /b 1 | |
:exitFromFunction | |
() | |
:end | |
endlocal | |
echo Finished successfully. |
This comment has been minimized.
This comment has been minimized.
@John-Blair Good question. I'm not sure why I set NEXT_MANIFEST_PATH and PREVIOUS_MANIFEST_PATH to be the same or if that's even needed. Maybe it was part of the boiler plate generated by kuduscript -- I don't remember. I did write about what I did in a post which you can view at https://alindgren.github.io/2017-12-17-deploying-to-azure-app-service-with-custom-build-script/ According to that, I actually ignore the manifest. I think I just copy everything from a temp build folder to the deployment target. |
This comment has been minimized.
This comment has been minimized.
Thanks for the feedback! I managed to get my copy folder across app services working using kudo's zip directory feature - powershell script in link in original comment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This comment has been minimized.
Hi,
I stumbled across this while looking for a way to copy a folder between a test and live app service on Azure.
Do you know if kudusync can be used to do this and how can i use it in a pipeline to do it?
Also I don't understand the point of the manifest files above - and why you set next and previous to be the same?
What does the content of this manifest file look like?
https://stackoverflow.com/questions/58580956/how-to-copy-a-folder-from-a-test-app-service-to-a-live-app-service-on-azure/58582499#58582499
Thanks.