迁移到新 Perforce 服务器的最佳方式是什么?

发布于 2024-07-24 02:11:02 字数 220 浏览 3 评论 0原文

我的家庭 Perforce 服务器死机了。 我设置了一个新的。

我设立它来支持的项目在规划阶段就夭折了。 当时仓库的内容是一些原型代码,我们从未制定灾难恢复计划。

开发机器上仍然保留着现有的代码。 尽可能地,我希望服务器的更改对开发人员来说是透明的——使用相同的存储库和相同的目录,只需更改要连接的服务器的名称即可恢复工作。

我需要做什么才能实现这一点?

My home Perforce server died. I set up a new one.

The project I set it up to support died in the planning phase. The contents of the depot at that point were some prototype code and we never got to setting up a disaster recovery plan.

The dev machines still have the existing code on them. As much as possible, I'd like the change of servers to be transparent to the developers--use the same depositories and the same directories, just change the name of the server to connect to and get back to work.

What do I need to do in order to make this happen?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

萌︼了一个春 2024-07-31 02:11:02

我假设您无权从死服务器访问 perforce depot 文件? 我假设您知道您将失去所有历史记录。

如果是这种情况,您需要做的就是设置新服务器,创建一个用户/客户端,其根 clientspec 路径与您的开发计算机上使用的原始 clientspec 相同,并将所有文件签入 perforce。 真的很简单...

您可能需要重新绑定 SCM 绑定,您可能在 Visual Studio 等工具中拥有该绑定,但仅此而已。

I assume you don't have access to the perforce depot files from your dead server? I assume you know that you will lose all your history.

If that's the case all you need to do is setup the new server, create a user / client with the same root clientspec path as your original clientspec was using on your dev machine and checkin all the files into perforce. Pretty simple really...

You may need to rebind is SCM binding that you may have in tools like Visual Studio but that's about it.

雪花飘飘的天空 2024-07-31 02:11:02

Shane 的建议将用一个人的文件版本填充仓库。 但是,如果您的其他用户也拥有副本,那么您将需要执行几个额外的步骤。

首先,按照 Shane 的建议设置一台机器。

您现在需要设置第二个用户。 如果您确信用户 2 的代码版本与您在新服务器中放入的版本完全匹配,则只需创建一个客户端规范(可能与之前使用的名称相同),然后使用“强制”标志进行同步。 这将覆盖用户 2 计算机上的所有文件,并且 - 更重要的是 - 确保 Perforce 知道您真正拥有的版本。

但是,如果您对代码中的任何差异有任何疑问,请不要从第二个用户的计算机进行初始同步。 相反,设置客户端规范,然后使用“协调离线工作”选项 - 从 P4V 选择工作区,然后右键单击选项。 然后只需浏览后续对话框即可找出您需要的内容。

最后,如果您想要一个非常快速的& 您的服务器的备份系统不干净,我在我的 博客此处 - 只需几分钟即可完成设置。

What Shane suggested will populate the depot with one person's version of the files. But if you have another user who also has a copy then you'll need a couple of extra steps.

Firstly, just set one machine up as suggested by Shane.

You now need to get the second user set up. If you are confident that the version of the code user 2 has exactly matches what you put in the new server, then just create a client spec (probably same name as used before), and then sync using the "Force" flag. This will overwrite all the files on user 2's machine, and - more importantly - ensure Perforce knows which versions you really have.

However, if you are in any doubt as to any differences in code, then do not do the initial sync from the second user's machine. Instead, set up the client spec, then use the "Reconcile offline work" option - from P4V select the workspace, then it's a right click option. Then just walk through the subsequent dialog to sort out what you need.

Finally, if you want a very quick & dirty backup system for your server, I've posted some notes on my blog here - should take you just a couple of minutes to set up.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文