如何部署Subversion外部？(How to deploy Subversion externals?)

如何部署Subversion外部？(How to deploy Subversion externals?)

我们正在用SVN测试水域，Beanstalk作为主机。 我们的设置看起来像这样：

存储库： 模块

模块1 模块2 第3单元

存储库： 网站1

自定义网站代码 svn：对模块1的外部引用 svn：对模块2的外部引用

存储库： 网站2

自定义网站代码 svn：对模块2的外部引用 svn：对模块3的外部引用

Beanstalk具有内置的FTP部署工具。 在我的理想世界中，Beanstalk只会看到外部引用，并随着网站更改部署任何对模块的更改，但这不受支持，并且不会很快 。

自动部署网站1和网站2的方法是什么，以便更改外部模块？

其他SVN主机是否更好地支持部署外部？

如果可能的话，我想避免添加我们自己的构建/部署服务器。

We're testing the waters with SVN, with Beanstalk as a host. Our setup looks something like this:

Repository: Modules

Module 1 Module 2 Module 3

Repository: Website 1

Custom website code svn:External reference to Module 1 svn:External reference to Module 2

Repository: Website 2

Custom website code svn:External reference to Module 2 svn:External reference to Module 3

Beanstalk has built-in FTP deployment tools. In my ideal world, Beanstalk would just see the external references and deploy any changes to the modules along with the website changes, but this isn't supported and won't be anytime soon.

What's a good practice for automatically deploying Websites 1 and 2 in a way that changes to the external modules are included?

Do other SVN hosts have better support for deploying externals?

If possible, I'd like to avoid adding our own build/deploy server.

最满意答案

如果部署使用导出，那么这可能是有道理的; 我很确定SVN的最新版本也导出了外部，但早期版本没有。 也许你最好的选择是在你的部署服务器上检查有问题的存储库并从那里更新？ 如果您使用分支和标记，您也可以在您的webroot上创建指向结帐中不同版本的符号链接。

If the deployment uses export, then that might make sense; I'm pretty sure the latest version of SVN also exports externals, but earlier versions did not. Perhaps your best bet would be to perform a checkout of the repository in question on your deployment server and update from there? If you use branches and tagging, you might also create symlinks to your webroot that point to different releases in the checkout.