多个开发人员如何有效地开发一个 force.com 应用程序? [英] How can multiple developers efficiently work on one force.com application?

问题描述

我工作的公司正在构建一个托管 force.com 应用程序，作为与我们提供的服务的集成.

The company I work for is building a managed force.com application as an integration with the service we provide.

由于 force.com Eclipse 插件提供的劣质工具，我们在处理同一组文件时遇到了问题.如果 2 位开发人员正在处理同一个文件，则会向其中一位发出无法保存的消息——一旦他合并，他必须手动强制插件将他的更改推送到服务器，同时单击 2 'Are you really sure'消息.

We are having issues working concurrently on the same set of files due to the shoddy tooling that is provided with the force.com Eclipse plugin. If 2 developers are working on the same file, one is given a message that he can't save -- once he merges he has to manually force the plugin to push his changes to the server along with clicking 2 'Are you really sure' messages.

基本上，如果其他人修改了他正在处理的文件，则每次开发人员想要保存时，该工具在合并更改方面做得很差.

Basically, the tooling does a shoddy job of merging in changes and forces minutes of work every time the developer wants to save if another person has modified the file he's working on.

我们目前正在通过让同事知道谁在编辑文件来基本上锁定"单个文件来解决这个问题.

We're currently working around this by basically 'locking' individual files by letting co-workers know who is editing a file.

感觉在这个时代必须有更好的方法.有谁知道我们可以使用不同的工具集、我们可以更改的流程，或者我们可以做些什么来使这更容易?

It feels like there has got to be a better way in this day and age. Does anyone know of a different toolset we could use, process we could change, or anything we can do to make this easier?

推荐答案

在使用 Force.com 平台时，我当前的组织发现可以根据具体情况采用多种不同的方法.我们都使用 Eclipse Force.com 插件没有问题，并且发现以下设置运行良好.

When working with the Force.com platform my current organisation has found a number of different approaches can work depending on the situation. We all use the Eclipse Force.com plugin without issues and have found the following set ups to work well.

我们有一个集中的版本控制系统，我们使用一系列 ant 命令将其部署到开发人员组织实例.然后，我们根据工作范围将其分成多个块，每个开发人员都有自己的开发组织并合并更改并定期测试它们，或者一起在一个开发组织中工作(如果您有 2 个开发人员应该不会主要问题)允许您几乎即时集成.

We have a centralised version control system that we deploy from using a series of ant commands to a developer org instance. We then depending on the scope of the work either separate it off into chunks with each developer having their own development org and merging the changes and testing them regularly, or working in a single development org together (which if you have 2 developers should be no major problem) allowing you to have almost instant integration.

如果你们都尝试处理同一个文件，那么无论如何都应该结对编程，但如果一起处理相似系统的两个组件，共享同一个组织可以让您通过创建快速灵活的方式进行开发您希望使用的系统的骨架，然后逐个充实细节.

If you are both trying to work on the same file you should be pair programming anyway, but if working on two components of a similar system together, sharing the same org can allow you to develop in a fast and flexible manner by creating the skeleton of the system you wish to use and then individually fleshing out the detail.

我已经广泛使用了这两种方法，我说，根据具体情况，效果非常好.

I have used both methods extensively and a I say, work really well depending on the situation.

这篇关于多个开发人员如何有效地开发一个 force.com 应用程序?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！