2016 has been an exciting year for our mission of helping customers to release applications at speed without compromising quality. We kicked off the year with the introduction of CA Release Automation Continuous Delivery Edition which was recently showcased as a key connecting point within CA’s market-first open and integrated ecosystem of continuous delivery solutions. A point well made in this great integrated CD ecosystem demo by Keith Puzey.
Today we announced the general availability of CA Release Automation 6.2, which contains product enhancements and new capabilities to make it easier than ever before to plan, coordinate and automate your continuous delivery pipeline at enterprise scale. We’ve added enhancements to automate the management of user permissions, introduced integrations to help you improve the quality of code before it reaches production, while adding support for the latest versions of Linux and Oracle. Click here to read the full details of these and other new capabilities.
One of the best aspects of my job is the opportunity to work directly with many of you on this journey towards continuous delivery. In fact, many of the concepts for CA Release Automation CD Edition came from listening to you, our users. As the number of application components and releases have dramatically increased, the number of dependencies and potential conflicts between releases have grown. In particular, we listened when you talked about the need for increased visibility to manage the growing number dependencies for each of your releases. Hi This is a critical area for many companies striving to achieve what my colleague, Benny Van de Sompele, calls readiness for continuous delivery. Put simply, having the ability to deploy a change to “any environment” at “any moment” fully “zero touch”.
As more and more of you move to the cloud and begin to implement modern new architectures such as microservices, the requirement for this type of automated dependency management capability becomes ever more apparent. Manual processes for managing dependencies and avoiding conflicts simply can’t keep pace with automated deployments. Critical dependencies can be overlooked or executed in the wrong order leading to release failures, which lead to slower delivery of critical capabilities to your end users, and ultimately, more resources and expense to triage the problem.
With v6.2, you can now define, track and enforce dependencies between applications and releases using the highly visual release pipeline dashboard of CDE. Moreover, you can now receive alerts when situations are detected for deployments that may jeopardize the implementation of new features. I look forward to hearing what you think. Join me on August 10 for a deeper dive on all the new features available with CA Release Automation 6.2.
In closing, I invite you to participate in our private feature advisory community so your input can shape what’s up next for CA Release Automation. Click here to join.