Adobe Looks to Drive DevOps Adoption via the Cloud


Adobe has been building out a managed service that includes continuous integration/continuous development capabilities on the Adobe cloud service. Now Adobe is extending the DevOps processes enabled by its CI/CD platform to make them more customizable in addition to expanding the scope of the application development tools it provides to include support for single page application (SPA) JavaScript frameworks.

Haresh Kumar, director of strategy and product marketing for mobile and connected experiences at Adobe, said DevOps processes are now an integral part of how Adobe enables customers to build a custom application experience using low-code tools it provides in Adobe Cloud. In the case of Adobe, that DevOps framework is made available via Cloud Manager, a feature of Experience Manager Managed Services that enables the streamlining of code development across staging and production environments in addition to providing code inspection, security validation and performance testing capabilities. Developers can now customize their CI/CD pipeline within Cloud Manager against specific key performance indicators (KPIs) they define.

Meanwhile, Kumar said the SPA Editor that Adobe provides is unique because front-end developers can preview a SPA to view JavaScript code and edit content including images, video and text. With this new capability, SPA content can be more easily edited and managed within the context of a business process, he said. The SPA Editor provided within Adobe Experience Manager currently supports the React and Angular frameworks, with plans to extend its reach to other frameworks underway.

While most IT professionals tend to think of DevOps processes only applying to large-scale applications, Kumar said it turns out that as organizations rely more on cloud services, vendors such as Adobe are exposing customers who want to create applications to a variety of best practices related to DevOps embedded within the cloud service. Many of the developers creating those applications may not recognize they are participating in a DevOps process, but Kumar noted that as more custom applications get developed on the Adobe platform, the number of web developers and content authors being exposed to DevOps process is starting to increase exponentially. It’s even probable many of those developers will be first exposed to DevOps processes within the context of a cloud service long before they encounter them within the context of their internal IT environments.

Kumar said a DevOps process managed by Adobe is enabling many organizations to smooth out what otherwise often can be a choppy digital business transformation. Building a new generation of customer experience applications requires access to modern tools that can transcend organizational silos spanning data that resides in sales, marketing and financial applications. Last month, Adobe announced it is acquiring Marketo, a marketing automation platform to facilitate that transition. Once that deal is closed, the DevOps framework Adobe has developed in the cloud will be extended to include the Marketo platform.

It’s hard to say to what degree Adobe will be able to drive adoption of DevOps processes across the Adobe Cloud platform. What might be even more interesting to see is how many of the organizations that rely on Adobe Cloud to develop applications will even realize they made the transition to DevOps.


Notify of

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x