Automated Release Management

[LasseGravesen]

Hi, We are investigating how to perform automatic release management on our environments because we are centralizing the ability to import releases on the environments. Specifically, right now the process controllers are manually importing releases onto the PROD environments whereas in the future it will be a single entity that does all the importing onto PROD environments. We need this because the amount of releases we are producing that will have to be imported will make it untenable to perform manually as soon as we move to the centralized model. We investigated using the command line tool, AutomateC.exe, that is available with Blue Prism however as it turns out you can only import processes and business objects, not releases with that. We understand that there is a higher level of complexity when importing releases and it would create a problem where endusers of Blue Prism would be able to shoot themselves in the foot, but we need the ability to import releases automatically moving forward.

[John__Carter]

As far as I'm aware we don't have plans for automated release import. Firstly, it would be pretty difficult because of all the questions (overwrite?, publish? etc) that may need answering, but probably more importantly, implementing a release into production should not be seen as a trivial matter. By automating it there is a risk it becomes casual behaviour, the recommended release procedures are not carried out, and eventually a disaster occurs. I've seen it happen. If you are really having that many releases, would it not be better to have a fixed implementation schedule, say once a week? Would that be less risky that implementing any time?