Question
Nationwide Building Society
GB
Last activity: 17 Jan 2025 8:43 EST
RPA 22.1 compatability with GitHub
Is the RPA 22.1 development platform compatible with GitHub version 2.45.2.windows.1
Accepted Solution
Updated: 3 Jul 2024 9:20 EDT
Pegasystems Inc.
US
@RichardB3397You may use any source control you prefer. We suggest using software that allows for exclusive locking to prevent the source control from merging any files as that process will corrupt your Pega Robotics files. There is no integration with the Pega Robot Studio UI with any source control, so you will need to use the UI or tools provided by the source control software to manage your files.
Updated: 16 Jan 2025 11:11 EST
Arbetsförmedlingen
SE
Hello @ThomasSasnett We also want to implement some kind of version control in our team. Which tool that Pega RPA recommends with v22.1? and why it doesn't have native integration with source code control tools? How does the version control is handled in Pega RPA studio, because I couldn't download the different versions from Robot Managers-->Packages. Can you please share if there is any documentation on how to integrate source code control tools, how to use them and maintain them. Thank you! /Rajesh
Pegasystems Inc.
US
@RajeshS17304030To answer your questions here, I will take them in order below?
Which tool that Pega RPA recommends with v22.1? - We do not have a specific one we recommend. We do require that you do not merge files, so choosing one with exclusive locking of files is a recommendation. We have seen customers use SVN, Git, Visual Source Safe, Bit Bucket, etc. They will all work fine assuming you do not allow them to merge files.
Why it doesn't have native integration with source code control tools? - There just hasn't been a real demand for this to be a top feature rather than other features that have and are being added to the developer experience. Most (if not all) popular source control systems have their own GUI or command line that works well for any source control, so using their interface is at the moment, the most effective way to use source control.
How does the version control is handled in Pega RPA studio, because I couldn't download the different versions from Robot Managers-->Packages? - Version control is not handled within Pega Robot Studio. After (or during) your development, you would simply use whichever tool you prefer to check-in your files. Before you begin work on your project, you would check out your files using whichever source control you prefer.
@RajeshS17304030To answer your questions here, I will take them in order below?
Which tool that Pega RPA recommends with v22.1? - We do not have a specific one we recommend. We do require that you do not merge files, so choosing one with exclusive locking of files is a recommendation. We have seen customers use SVN, Git, Visual Source Safe, Bit Bucket, etc. They will all work fine assuming you do not allow them to merge files.
Why it doesn't have native integration with source code control tools? - There just hasn't been a real demand for this to be a top feature rather than other features that have and are being added to the developer experience. Most (if not all) popular source control systems have their own GUI or command line that works well for any source control, so using their interface is at the moment, the most effective way to use source control.
How does the version control is handled in Pega RPA studio, because I couldn't download the different versions from Robot Managers-->Packages? - Version control is not handled within Pega Robot Studio. After (or during) your development, you would simply use whichever tool you prefer to check-in your files. Before you begin work on your project, you would check out your files using whichever source control you prefer.
We don't really have any documentation around how to use any source control tools as Pega Robot Studio really is not restricted to any specific ones. Feel free to use whichever one suits your needs best. Just remember not to merge files. I generally do this by assigning developers to different assets to prevent anything one developer is working on from needing resources from another. If you must work within the same project, then the Globals is usually the one piece that is shared and requires some forethought to ensure each developer only updates the main copy once before making the other developers download a new copy.