We are using Outsystems platform for our development activity. So far, there was one team, which involved in development. Now there is one more team has been formed to implement the change request and defect fixes. What we would like to achieve here is we want to have the outsystems files maintained in source code management system like SVN, do the branching for different team who works in different development activity say one team implementing of change request and other team implementing defect fixes. Any team whose code mode to production has to merge the code with trunk and other team who is still doing the development should merge the recently moved production changes with the ongoing development branch code. To keep it simple, can we maintain trunk, branch in version control system like SVN and merge code from trunk to branch or branch to trunk whenever needed.
I would also like to know if we can merge the two different version of outsystem code with traditional source control system.
Are you on outsystems trial? What you are referring to is possible to achieve from within outsystems platform, a complete ALM in fact.
Two perspectives on that, from Service Studio (code merge) and Lifetime (Deployments):
I suggest you go the "outsystems way" first and think if you really need something else.
Thanks for your reply. We use licensed version. Client wants to ensure that code to be maintained in version control system like any other traditional language code throughout the organisation. Therefore, checking the feasibility of maintaining the code in version control system.
Short story: you cannot do that. OutSystems is not a traditional programming language or environment, and it does not have or support traditional version control. It has built-in version control (as you may know), and that's all you need to work with (and all you can work with).
Thanks Kilian for the information.