undefined
undefined

Reputation: 34299

Kudu post-deployment commands not running

I'm trying to run some scripts after my site is deployed to azure (via kudu)

I have the following directory structure

-solution
  - .deployment
  - deploy.cmd 
    - deployment
       - postdeployactions
         - test.bat

.deployment looks like this:

[config]
POST_DEPLOYMENT_ACTION_DIR  = deployment\postdeployactions\
command = deploy.cmd

deploy.cmd is unmodified from the one generated by azure site deploymentscript --aspWAP pathToYourWebProjectFile.csproj -s pathToYourSolutionFile.sln (http://blog.amitapple.com/post/38418009331/azurewebsitecustomdeploymentpart2/#.VPYd_PmUeTI)

However test.bat is not getting called.

I have tried setting both POST_DEPLOYMENT_ACTION_DIR and SCM_POST_DEPLOYMENT_ACTIONS_PATH (see https://github.com/projectkudu/kudu/issues/1154)

Upvotes: 2

Views: 1674

Answers (2)

Andy Mehalick
Andy Mehalick

Reputation: 993

I do exactly the same thing but instead of POST_DEPLOYMENT_ACTION_DIR I use SCM_POST_DEPLOYMENT_ACTIONS_PATH, could that be the issue?

[config]
SCM_POST_DEPLOYMENT_ACTIONS_PATH = deployment\postdeployactions\

Upvotes: 0

dmoreno
dmoreno

Reputation: 100

Some "Site Extensions" reconfigure this behaviour inside Azure.

For example, if you use Composer Site Extension in a PHP Web Site, default kudu deployment script is replaced by other script injected by Composer Site Extension.

Maybe this could be your case.

Look at your COMMAND environment variable.

Upvotes: 2

Related Questions