When Multiple Developers want to work with Same OpenSpan Solution in SVN at a time .how other user changes(e.g: Interrogation ,added extra automations into same adapter ,added extra components ,activities, scripts etc.) will reflect into the same solution after check-in & checkout. Also how to track what other user has changed.
But we're facing an issue if 2 or more users interrogate the controls in the same adapter and tries to commit the code to SVN, that time SVN is failing to merge the data. Other than that we haven't faced any issue with SVN.
For this, I can suggest 1 thing. Always interrogation has to taken care by single user in the team.
You cannot allow SVN to merge any of the Pega Robotics code. Each item must be checked out and locked by the developer working on it. When they finish, then the next developer can check out the updated copy and modify it, but changes cannot be merged using source control.
Since the developer writing the automations needs to understand how the adapter works, we typically assign one developer to each adapter. This way, they perform the interrogation as well as the automation. This is the most efficient way we have found to allocate resources.