AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
“Jason”, “Shauna” and Content developer (“Scott”) can interact with content and its dependencies in a way that maintains a single copy of all shared/embedded content.Cloud Administrator (“Jason”) and/or Release Manager (“Shauna”) are able to replicate content from a Central repository across various product instances or tenants.The architectural diagram below illustrates how vRLCM supports CDLC:Īs with SDLC where there are different roles (Developer, Release/Build manager), CDLC also supports dedicated user roles (with persona code names attached for simplification): Similar to Software Development Life Cycle (SDLC) where multiple developers check-out source code from SCM repository (such as Git/GitLab), modify it in their Development environments, perform unit tests, check modified source code into repository for it to be deployed to production, vRealize Suite LifeCycle Manager (vRLCM) provides functional support for conceptually similar Content Development Life Cycle (CDLC) with its internal Common repository and integration with external SCM systems and embedded vRealize CodeStream for code delivery stages (Capture, Test, Release) automation. Introduction: IaaS Content Development Lifecycle Here we will be focusing on implementing the main part of Multi-developer story for IaaS as code: how to enable developers to work with IaaS content similar to how “regular” software developers work with traditional source code. In the previous blog we have shown step-by-step process on how to set up IaaS content development environment using vRealize Automation with Infrastructure blueprint that is available for download from vRA 7.4 appliances. We are continuing to cover the multi-developer story for IaaS contents as a code. This post was originally published on this site.
0 Comments
Read More
Leave a Reply. |