In the past few years, I have been involved in several ROM Assessments for Customers.
In many cases, I have observed that most of the Release management activities are done manually either by the support team or with the developer's assistance. This kind of deployment leaves a loophole which is a red flag during audits with the possibility of unwanted problems later for large production changes like upgrades.
This got me thinking to my old SOA deployment days where we corrected this problem with Jenkins Auto deployment using GIT as the code repository. We also had a pipeline implemented for approvals to higher environments. Recalling that, I worked on a demo for a similar implementation for Blue Prism.
Adding the guide with a few notes as an attachment to this post.
Hope it helps someone.
------------------------------
Ashish Easow
Senior Consultant - Professional Services
Blueprism
------------------------------
