You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started: AI Resources for Oracle Cloud HCM – Go Here

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here

VBS - Best Way to handle Migration when Working on Multiple Developments

edited Jun 13, 2025 12:34PM in Visual Builder Studio for HCM 15 comments

Summary:

There are multiple threads on this topic. We have gone through some of the recommended approaches and realized each - way of handle development and migration has its own shortcoming. Below mentioned the use-case of our business for HCM and ways + struggles we are facing .

Content (please ensure you mask any confidential information):

Oracle has mandate to migrate to Redwood in 25C. Thus, we, being in 25B are migrating + validating all existing customization from RUI to Redwood; some through Migration Tool, and some manual - whichever is faster.

Our Plan - Main to be reserved for Prod deployments only. That means, only specific changes which are going to prod, will be pushed to main and then to Prod. Intention is to keep mainline intact as this is a single source of truth for changes existing in Prod.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!