Blue Prism visual studio have an option to integrate with any source code repository such as SVN, TFS, GIT, etc This features allow the developer work on parallel on the same process
As of now, to manage the code and versioning the inbuilt functionality of BP studio is being used. With that approach it is quite difficult to do an end to end DevOps.
It would be great from the software cycle and project management perspective if there was an integration between BP studio and Git hub or svn
Currently, my solution (in theory as of posting this) is to have a upsert trigger in SQL Server which extracts the XML into a watched folder directory. When new files are created in this watched directory a command line is executed to do a commit and push to the git repo. From there it is normal DevOps where upon a build task would call a CLI command to export a release and then subsequently import to the next environment. Again, all in theory.
Anyway, here's to hopes that there is an option for an integration with an SCM platform.
I'm adding my comment to this idea as I initially commented on what is now identified as a duplicate idea as to make sure all dialog is seen.
Currently, my solution (in theory as of posting this) is to have a upsert trigger in SQL Server which extracts the XML into a watched folder directory. When new files are created in this watched directory a command line is executed to do a commit and push to the git repo. From there it is normal DevOps where upon a build task would call a CLI command to export a release and then subsequently import to the next environment. Again, all in theory.
Anyway, here's to hopes that there is an option for an integration with an SCM platform.
A native source control is a necessity to manage code in a multi team environment. Ideally an automated deployment system e.g. Octopus to promote code in higher environments will have reduce load of manual release management.
Thanks so much for submitting your idea! We are moving it into theUnder Considerationstatus while we route the idea through our internal review process.
We will update you as your idea moves along the lifecycle.
Voted up. Agree, this is almost a necessity for large development teams/projects. Without the ability for multiple resources to work on a process together every project is done on a 1-to-1 ratio. Can't believe this doesn't exist and that it's taken this long to get this requirement considered. It's essential.
Also voted up. This is an almost necessary feature while working in bigger teams. Right now many problem can accure especially when multiple persons are working on the same process/business object or while doing hotfixes on prod. This would be also a major improvement for rollbacks. Although It's already possible to rollback a process or object to a previous version by opening the old version in comparison view, exporting and reimporting it, with a repository it would be much easier.
