In the dynamic landscape of Automation, effective release management plays a pivotal role in enabling organisations to maintain control over their Automation deployments. CORTEX, with its comprehensive release management capabilities, empowers organisations to define and track Automation versions running in production environments, ensuring a managed and controlled evolution of their technology infrastructure.
Watch our video to Stephen and Eddie to find out more. You can also read the full transcript below.
Stephen Connor:
Release Management is really important for organisations so that they can control which version of the Automation is actually running in production at any point in time. And so being able to define which users are able to publish Automation to production environments is part of that Release Management process. But also, tracking the versions of the, the automations that are in production is critical as well. So at any point in time, you know, which version is live. Being able to publish multiple versions of the same automation to a production environment is really powerful, because it lets organisations evolve the rest of their technology infrastructure in a managed and controlled way. Without it being a big bang type of approach.
Eddie Watson:
I think, another aspect of this is effectively the community that you create, where everybody can contribute to that process. So there’s the concept of the sandbox where the individual gets into the sandbox, and he has carte blanche to do what he likes, and they can create, test, as soon as they put that into the master repository, it allows other people to see that and to difference, that master version against their version, so that you allow this community to develop of people who have access to that and are part of their communities, whether it’s Nokia, Cisco, or the HR to actually work together in a coordinated managed fashion to create a master version of an Automation, which can then go through the governance process of what you’ve explained already, which is to deploy out into the live environment, whatever version you want, that’s appropriate for the installation that it’s going into. I think that those aspects all contribute towards making the concept very powerful.
