Blue Prism with GitHub, Possible? Version Control

#1
Hi all,

First time poster, long time lurker here.

I was just wondering if anybody had any experience with Blue Prism and GitHub, and if it is possible to create a version control?

Today, as far as i know, the only "version control" Blue Prism has is Packages (This is not what i want to discuss). However, when i create a release for my package, and then import it to a new environment, i lose all the save-logs.

So lets say i want to keep all the data: save logs, process, objects, queues and other configurations in system, is it possible to do that in GitHub or any other way? Basically, is there a better version control available than packaging?

Thank you in advance :)
 
#2
Hi,

I guess that GitHub would not be a good decision for Blue Prism as a version control system, as it's packages are in xml format. Blue Prism has some kind of it's own version control system: by choosing several versions in Process Studio you can compare them.

Regards
 
#3
Hi,

I guess that GitHub would not be a good decision for Blue Prism as a version control system, as it's packages are in xml format. Blue Prism has some kind of it's own version control system: by choosing several versions in Process Studio you can compare them.

Regards
Sorry but i am not sure what you mean with "choosing several versions in Process Studio you can compare them" ? Could you try to explain in detail how that would work? The only way i can think of is to either
  • Open each save and look at the changes
  • Or whenever i do a change, "Save as" the file and create a new one
  • And of course packages like mentioned above.. but then again. Wont have history.
Is there another way?
 
#4
Sorry but i am not sure what you mean with "choosing several versions in Process Studio you can compare them" ? Could you try to explain in detail how that would work? The only way i can think of is to either
  • Open each save and look at the changes
  • Or whenever i do a change, "Save as" the file and create a new one
  • And of course packages like mentioned above.. but then again. Wont have history.
Is there another way?
Yes.

In Process Studio, select 2 versions of a process and right click, then choose Compare. It will show you the differences between the 2 versions. Also works for Objects.

You can use this to create a kind of rollback functionality by exporting the older version of the process.
 
#5
Yes.

In Process Studio, select 2 versions of a process and right click, then choose Compare. It will show you the differences between the 2 versions. Also works for Objects.

You can use this to create a kind of rollback functionality by exporting the older version of the process.
I see. Thank you!

Having a good folder structure might be key with that technique when you're working on many objects and processes (or big ones).
 
#6
Hello ! Good discussion. Beyond compare BO codes, I have to manage lot of sources in a Automation. For example, Excel VBA, Powershell etc. In this case, the BP Control Rom is not a repository. Git for example is a good way. Are there any fashion to easy integrate ?
 
#7
There is no way that I'm aware of to integrate BP with GitHub, nor would doing so provide the source control functionality that you're looking for. BP's source control consists solely of the previous versions of a process or object that are stored in the BP database and viewable in Studio.

Since true source control is lacking within BP, at my company our policy is to always include all components of an automation in every release, even if we only need to overwrite 1 component. This way, every release we generate is a rollback point if we need it.
 
Top