使用 PVCS 实现项目部署自动化
我们使用 PVCS 对所有代码进行源代码控制。 我们在欧盟拥有 7 个服务器，覆盖 17 个国家。 PVCS 模仿我们在生产中的文件夹结构：
folderA
|
|--folderB
| |
| | -- folderC
| |
| | -- folder
| --folderD
| |
| | -- folderE
| |
| | -- folderF
我们的项目可能依赖于多个文件夹中的文件，因此我们只需复制一个文件夹即可部署新项目。 多个程序也可以存在于同一个文件夹中。
我们有 DEV、UAT 和生产服务器。 文件将在DEV服务器上开发，放到UAT上（他们应该这样做，这是问题的一部分，涉及太多人手，其中一些人不想玩球），供用户测试。 当 UAT 获得批准后，它们将被放回到 PVCS 中，并带有适当的版本标签，并分配一个开发级别（它们可以更早地带有开发版本标签放回到 PVCS 中）。
当所有相关批准完成后，将提出变更控制请求，支持团队将代码部署到生产中。
我们最大的问题是这个过程是如此琐碎，有太多的人必须在特定的时间做某些事情并以正确的顺序告诉人们事情。
我们想要的是一个能够自动化项目部署的程序。 您需要能够为 PVCS 中不同文件夹中的不同文件分配项目标签，然后能够继续该标签并根据需要部署所有文件。
这存在吗？
我希望这是有道理的。
谢谢乔恩
编辑：
我们会一直创建新项目。 项目与部署相关。 即项目 1234 将使用文件 1、2、5、6，项目 2345 将使用文件 2、5、8。 因此，为此，我们需要一种快速、简单的方法来添加和管理项目。
如果有人能提出一种更好的方法来处理这种自动化，那就太好了。
我们对编译代码和测试不感兴趣，因为有多种语言，我相信此时这超出了我们的范围。
We use PVCS for source control for all our code. We have 7 Servers across the EU covering 17 countries. PVCS mimics our folder structure in production:
folderA
|
|--folderB
| |
| | -- folderC
| |
| | -- folder
| --folderD
| |
| | -- folderE
| |
| | -- folderF
Our projects can be dependant on files in multiple folders so we can just copy one folder out to deploy a new project. Also multiple programs can live in the same folder.
We have a DEV, UAT and Production server. Files will be developed on the DEV server, put onto UAT (well they are supposed to, this is part of the problem, too many human hands involved and some of them don't want to play ball), for testing by the user. When UAT is approved they are put back into PVCS with the appropriate version label and assigned a development level, (they can be put back into PVCS earlier with a development version label).
When all the relevant approvals have been done a change control request is raised and the support team will deploy the code to production.
Our biggest problem is the process is so bitty and there are too many people that have to do certain things at certain times and tell people stuff in the right order.
What we would like is a program that would automate the deployment of projects. You would need to be able to assign different files from different folders in PVCS a project label and then be able to progress that label and deploy all the files as needed.
Does this exist?
I hope that made sense.
Thanks
Jon
EDIT:
We would be creating new projects all the time. A project would relate to a deployment. I.e. project 1234 would have files 1,2,5,6 project 2345 would use files, 2,5,8. So to this end we would need a quick and easy way to add and manage projects.
If anyone can suggest a better way of dealing with this sort of automation that would be great as well.
We are not interested in compiling the code and testing as there are a number of languages and I believe that would be way out of our scope at this point.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
查看 nAnt 和 巡航控制
编辑：
借助 Cruise Control，您始终可以编写自己的插件来更好地处理您的环境。
Check out nAnt and Cruise Control
edit:
With Cruise Control you can always write your own plug ins to better handle your environment.
PVCS 可以实现自动化。 我组织中的软件工程人员创建了一整套与 PVCS 配合的脚本。 我们使用这些脚本来自动化我们的软件集成和发布过程。
例如，我们有一个创建发布的脚本，这意味着使用来自许多项目和数据库的特定版本的文件创建一个新项目。 听起来和你想做的很相似。
PVCS can be automated. The Software Engineering people in my organization have created a whole set of scripts to go along with PVCS. We use these scripts to automate our SW integration and release process.
For example, we have a script to create a Release, which means creating a new project with specific versions of files coming from many projects and databases. Sounds similar to what you want to do.
为了自动化我们的部署过程，我必须使用 pcli 和 python 创建一个工具。 pcli 脚本获取代码（使用用户的输入（标签））和 python 来部署到我们的服务器。
检查 VM_Install_Dir\books\vm\vmbooks\pcli.pdf 下的 pcli 文档
In order to automate our deployment process i had to create a tool using pcli and python. Where the pcli script get the code ( using inputs from the user ( Labels ) ) and python to deploy to our servers.
Check for the pcli documentation which is under VM_Install_Dir\books\vm\vmbooks\pcli.pdf