我有一个Azure函数的自定义批量部署脚本,它过早结束而不会出错。我希望有人能帮助我理解正在发生的事情。Azure函数/ Azure网站自定义部署脚本过早结束
有问题的部分似乎是脚本的“预部署”部分中:
for /F %%f in ('git.exe diff --name-only %PREVIOUS_SCM_COMMIT_ID% %SCM_COMMIT_ID% ^| grep package.json') do (
SET PACKAGEJSON=%%~f
SET PKGFOLDER=!DEPLOYMENT_SOURCE!\!PACKAGEJSON:package.json=!
echo "NPM Install: !PKGFOLDER!package.json"
pushd "!PKGFOLDER!"
npm install --production --progress=false --cache-min=432000
npm install --save json-loader --progress=false --cache-min=432000
IF !ERRORLEVEL! NEQ 0 goto error
popd
)
如果的package.json尚未最后两次提交之间修改,脚本跳过这一部分作为预计并继续执行“部署”部分。
如果package.json已被修改,则代码首先按预期工作,然后运行npm安装。然而,然后,它结束时没有错误,并且不会继续到部署部分。在最后一次npm安装运行后,脚本没有额外的输出。
任何人都可以帮助我了解什么是错的?这对我来说是正确的。
完整的脚本如下,它是下列项目的一部分: https://github.com/securityvoid/.deploy
@if "%SCM_TRACE_LEVEL%" NEQ "4" @echo off
@echo Started: %date% %time%
:: ----------------------
:: KUDU Deployment Script
:: Version: 1.0.12
:: ----------------------
:: 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%.
)
echo "Deployment Source: %DEPLOYMENT_SOURCE%"
IF NOT DEFINED DEPLOYMENT_DIST (
SET DEPLOYMENT_DIST=%DEPLOYMENT_SOURCE%\dist
) ELSE (
ECHO "Deployement Dist already set"
)
echo "Deployment Dist: %DEPLOYMENT_DIST%"
IF NOT DEFINED DEPLOYMENT_TARGET (
SET DEPLOYMENT_TARGET=%ARTIFACTS%\wwwroot
)
echo "Deployment Target: %DEPLOYMENT_TARGET%"
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
)
for /F "tokens=5 delims=.\" %%a in ("%PREVIOUS_MANIFEST_PATH%") do SET PREVIOUS_SCM_COMMIT_ID=%%a
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Pre-Deployment
:: ----------
@echo "Initiating Pre-Deployment: %date% %time%"
@echo "Previous Commit: %PREVIOUS_SCM_COMMIT_ID% Current Commit: %SCM_COMMIT_ID%"
for /F %%f in ('git.exe diff --name-only %PREVIOUS_SCM_COMMIT_ID% %SCM_COMMIT_ID% ^| grep package.json') do (
SET PACKAGEJSON=%%~f
SET PKGFOLDER=!DEPLOYMENT_SOURCE!\!PACKAGEJSON:package.json=!
echo "NPM Install: !PKGFOLDER!package.json"
pushd "!PKGFOLDER!"
npm install --production --progress=false --cache-min=432000
npm install --save json-loader --progress=false --cache-min=432000
IF !ERRORLEVEL! NEQ 0 goto error
popd
)
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Deployment
:: ----------
@echo "Initiating Deployment: %date% %time%"
:: 1. Build Script
node %DEPLOYMENT_SOURCE%\.deploy\deploy.js
:: 2. KuduSync
IF /I "%IN_PLACE_DEPLOYMENT%" NEQ "1" (
call :ExecuteCmd "%KUDU_SYNC_CMD%" -v 50 -f "%DEPLOYMENT_DIST%" -t "%DEPLOYMENT_TARGET%" -n "%NEXT_MANIFEST_PATH%" -p "%PREVIOUS_MANIFEST_PATH%" -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.
结束前需要多长时间?它总是一样吗?此外,您的应用程序处于消费模式还是应用程序服务计划模式? –
消费模式,其相当快。花大约60-90秒运行NPM命令。它并不总是相同的确切时间段。我也将SCM_COMMAND_IDLE_TIMEOUT增加到了900秒。 – Doug
不知道发生了什么事。有一点需要检查的是Kudu w3wp是否会崩溃。你可以在Kudu进程管理器之前和之后看看PID是否改变(对于scm)。 –