Source control for Open span
Hi,
can anyone let me know which source control (GIT, TFS, or any other) is best or a good fit for the openspan project?
Thanks,
Jay
***Updated by Moderator: Marissa to update categories***
Accepted Solution
Pegasystems Inc.
US
Hey guys,
The key to source control with Pega Robotics is to understand that there is no way to merge different versions of a file so it is crucial that any file checked out is locked so no one else can edit it. Any source control system that implements pessimistic locking will be fine. I hope this helps.
Cecil Howell, CSA | Senior Instructor | Pegasystems Inc.
RBC
CA
I'd echo this request asking how should a project be managed by multiple people.. I make a change in one .aos, and Jay makes a change in another. How doe we keep everything in sync if Git doesn't fit the tool...
Accepted Solution
Pegasystems Inc.
US
Hey guys,
The key to source control with Pega Robotics is to understand that there is no way to merge different versions of a file so it is crucial that any file checked out is locked so no one else can edit it. Any source control system that implements pessimistic locking will be fine. I hope this helps.
Cecil Howell, CSA | Senior Instructor | Pegasystems Inc.
Pegasystems Inc.
US
Generally, we use SVN mainly out of convenience, but it does have locking capabilities to prevent users from editing files that are being edited by others. Typically, with multiple developers, each are assigned different parts of the project to minimize any sharing of the project pieces. Basically, developer A will work on the controller project where all of the logic and architecture is located, while developer B will work on an adapter project where she/he creates automations that are only applicable to the one adapter. Since each developer is working on a separate project, there are minimal areas for conflict.