持续/自动化部署对于桌面应用程序有意义吗？
我目前正在开始阅读书 持续交付 由 Humble/Farley 提供，虽然其中的很多内容都有意义，但有一点令人烦恼我：
看来作者只是针对基于服务器（单客户端？）的应用程序（如 Web 应用程序）来处理要做什么和避免 wrt。自动化构建过程、测试、部署。
查看标记为 连续部署 的问题，该术语似乎仅在基于服务器的应用程序上下文中使用。
所以，我想知道，在创建桌面应用程序的“设置”（谈论 Windows 应用程序）之后自动化操作是否有意义？桌面应用程序的“部署”始终是用户驱动程序，那么在这里自动化任何东西有什么意义——而且，实际上，什么东西可以被自动化，才有意义呢？
哦，顺便说一句。我完全不确定这个问题是否最好放在 programmers.SE 上，所以如果您认为可以，请随意将其移至那里.
I'm currently starting reading the book Continuos Delivery by Humble/Farley and while a lot of stuff in there makes sense, there one thing that's nagging me:
It does seem the authors are solely targeting server-based (single-client?) applications (like webapps) with their treatment of what things to do and to avoid wrt. automating the build process, the testing, the deployment.
Looking at the questions tagged continuous-deployment it does also seem the term is only used in context of server-based applications.
So, I was wondering, does automating stuff after "the setup" (talking of a windows app) for a desktop app has been created even make any sense? The "deployment" of a desktop app is always user-driver, so what kind of sense would it make to automate anything here -- and, really, what stuff could be automated that made any sense?
Oh, and btw. I'm entirely unsure whether this question would be better put on programmers.SE, so feel free to move it there if you think it would.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
请检查链接：http://timothyfitz.wordpress.com /2009/03/09/cd-for-client-software/ 讨论可下载软件的持续部署。
Please check the link: http://timothyfitz.wordpress.com/2009/03/09/cd-for-client-software/ which talks about Continuous Deployment for Downloadable Software.
简短的回答是肯定的。
如果您正在开发在组织中的台式电脑上运行的自定义代码，则可以自动将已通过所有测试的最新版本推送到所有客户端电脑。
然而，您几乎肯定需要确保部署过程不会破坏用户体验；这是设计应用程序时必须考虑的问题。此外，您还需要确保您的网络可以支持每天将必要的文件推送到这些计算机 X 次。桌面通常不像服务器那样连接。
The short answer is Yes.
If you are developing custom code that's running on desktop PCs in your organization then it would be possible to automatically push the latest build which has passed all tests to all client PCs.
However you would almost certianly need to ensure that the deployment process was not disruptive to the user experience; this would be something which had to be considered when designing the application. Also, you would need to ensure your network could support pushing the necessary files to those machines X times per day. Desktops typically not are connected as well as servers.
我们有同样的问题。我们希望能够持续部署我们的桌面应用程序。
Google 有一个名为 Omaha 的开源库，用于帮助默默更新 Chrome。不过，要在您自己的应用程序中获得无缝体验，需要做大量的工作。
我们实际上正在构建一项服务，希望能够使持续部署任何桌面应用程序变得更加容易。目前，我们正在尝试与尽可能多的潜在用户交谈，以确保我们构建正确的产品。如果您有兴趣，可以访问 QuietDeploy.com 了解更多信息
对自我推销表示歉意，但希望如此这有点有趣。
We have the same problem. We'd like to be able to continuously deploy our desktop apps.
Google have an open source library called Omaha they use to help silently update Chrome. It takes quite a bit of work to get as seamless an experience in your own app though.
We're actually building a service that will hopefully make it much easier to continuously deploy any desktop application. We're trying to speak to as many potential users as possible at the moment to make sure we build the right thing. If you're interested you can find out more at QuietDeploy.com
Apologies for the self promotion, but hopefully it's of some interest.