Welcome to the third part in the series working with the vRealize Build Tools. At this stage, you should have a fully working CI infrastructure and have all of your vRO code exported using packages and stored in Git repositories. In this post, I will show you how to manage dependencies across your packages and how you can use the
Category: Artifactory
DevOps JavaScript Visual Studio Code vRealize Build Tools Maven Development Artifactory VMware Git vRealize Orchestrator
IaC for vRealize: Manage Existing vRO Code With vRealize Build Tools & Set up Git Repositories
In my previous post on Deploying vRealize Build Tools To Allow Infrastructure As Code for vRA and vRO, I covered how to set up the CI infrastructure and your developer workstation, in preparation for managing your vRO code as projects with Visual Studio Code and Maven. In this post, I will explain how you can work with your existing code
JavaScript Development Visual Studio Code VMware vRealize Build Tools vRealize Automation Maven Artifactory vRealize Orchestrator DevOps
IaC for vRealize: Deploying vRealize Build Tools To Allow Infrastructure As Code for vRA and vRO
As any vRealize Orchestrator developer will tell you, managing code outside of the appliance is difficult. I recently wrote a post about Using Visual Studio Code for your vRealize Orchestrator Development, where I highlighted some of the challenges with this. The issue is that we’re not given the freedom to use any IDE we want, easily run unit tests on