Azure KUDU部署在指定deploy.cmd时忽略项目设置

时间:2015-05-25 20:31:30

标签: azure-web-sites kudu

我的nodeJS repo中有一个自定义.deployment文件,如下所示:

[config]
project = src/portal
command = deploy.cmd

如果我删除command设置,则会尊重project设置。但是,我需要自定义部署脚本来执行一些bower和grunt命令。每当我重新添加command参数时,Azure / KUDU似乎忽略了project设置。我已恢复使用azure site deploymentscript --node生成的默认deploy.cmd脚本,以确保我的自定义不是问题。问题仍然存在。我错过了什么吗?

作为参考,这是来自azure的KUDU输出:

remote: Updating branch 'master'.
remote: Updating submodules.
remote: Preparing deployment for commit id '3f92585db0'.
remote: Running custom deployment command...
remote: Running deployment command...
remote: Handling node.js deployment.
remote: KuduSync.NET from: 'D:\home\site\repository' to: 'D:\home\site\wwwroot'
remote: Looking for app.js/server.js under site root.
remote: Missing server.js/app.js files, web.config is not generated
remote: The package.json file does not specify node.js engine version  constraints.
remote: The node.js application will run with the default node.js version 0.10.32.
remote: Finished successfully.
remote: Deployment successful.

1 个答案:

答案 0 :(得分:3)

这是设计使然,当您拥有自定义部署脚本时,您可以完全控制部署,因此project属性没有意义。

如果您需要其他项目,只需使用您需要的内容更新自定义部署脚本。