Welcome to the VB Studio Lifecycle Management Learning Path – a collection of blogs, documentation, and office hours sessions designed to help you manage the full lifecycle of Oracle Cloud extensions using VB Studio.

In this series, we walk through how extensions are structured in Git, how teams collaborate using branching and merge strategies, how to move changes safely from Dev to UAT to Production, and how to handle Oracle’s quarterly updates without breaking what’s already in place.

This blog is structured for teams who already know how to build extensions and now need to operate them safely across environments and release cycles.

We’ll keep updating this learning path as new content and resources become available.

Who this is for

  • Implementation teams extending Oracle Fusion Cloud Applications with VB Studio
  • Release managers and Dev Ops teams governing extension promotion
  • Developers handling Git branches, merge requests, and deployment troubleshooting
  • Administrators responsible for environment setup, OAuth configuration, and production readiness

The Learning Path

Module 1: VB Studio Fundamentals

Start here if you’re new to how extensions move from local development to production. Before diving into branching strategies or deployment plans, it’s important to first understand how VB Studio is structured.

At a high level, a project is the main container-it holds your Git repositories, CI/CD pipelines, environment references, and team workspaces. A workspace is your personal development area, tied to a local Git branch that syncs with the remote repository when you publish. Environments refer to the registered Oracle Cloud Application instances (Dev, Test, UAT, Prod) where extensions are deployed.

In this module, we’ll walk through:

  • The end-to-end extension lifecycle from personalizing through production promotion
  • How extensions are created, reviewed, merged, published, and promoted
  • Key concepts like projects, workspaces, repositories, branches, merge requests, builds, and environments
  • What happens to extensions during quarterly updates and patches

Suggested reading and viewing:

Module 2: Branching Strategy and Best Practices

Branching is the single most consequential decision a VB Studio team makes. Get it right and parallel work flows; get it wrong and every release becomes a merge negotiation.

The hardest part isn’t picking a branch model – it’s getting every team to follow it consistently. Standardize at the program level and document it as part of your operating model.

This module covers:

  • When to use feature, review, integration, and main branches
  • How to keep long-running branches in sync without painful merges
  • How to minimize merge conflicts before they happen
  • How to protect main from direct changes
  • How branch strategy adapts when multiple applications or pillars (HCM,SCM, Talent) operate on different release timelines

Suggested reading and viewing:

Module 3: Merge Requests and Conflict Handling

Merge requests are where different pieces of work come together-and sometimes conflict. You only really understand your process when you’ve had to deal with a messy merge.

A few simple practices can make this easier. Keep your branches short-lived so they don’t drift too far. Pull changes from the integration branch regularly while you’re still working, instead of waiting until the end.

When conflicts do happen, don’t rush through them. Take a moment to understand what’s going on. For example, conflicts in extension.json are often more than just text issues-they can point to problems with versioning or deployment order.

The goal isn’t just to resolve conflicts quickly, but to understand them so you can avoid the same issues later.

This module covers:

  • Creating merge requests and reviewing changes before merge
  • Handling merge conflicts in code and metadata
  • Resolving extension.json version conflicts specifically
  • What to do when review branches are updated after integration has already moved ahead
  • When to rebase, when to merge, and when to recreate a branch from scratch
  • How to avoid silently overwriting another team’s work

Suggested reading and viewing:

Module 4: Deployment and Migration Across Environments

Once your branching strategy is in place, the next step is moving code between environments in a safe, predictable way. It’s not just about “deploying to the next environment.” You need to know what’s actually ready, what’s still in progress, and whether everything lines up-like environment setup such as OAuth still working.

VB Studio offers two operating models for promoting extensions, and the choice between them is more strategic than it looks.

Manage Extension Lifecycle (MEL) is the simpler path. The MEL page gives a unified view of all environments, all extensions, version history, dependencies, and one-click deploy/promote and importantly, deployments made from MEL bypass any CI/CD pipelines. For most teams running standard Fusion extension work, MEL is the right default. It’s centrally visible, fast, and removes pipeline complexity from the day-to-day.

This module covers:

  • Deploying from Dev to Test, and from Test to Production
  • Managing deployments across multiple applications and projects
  • Using OAuth for environment setup and deployment automation
  • What to do when production and non-production are not on the same code line

Suggested reading and viewing:

Module 5: Rollback, Recovery, and Production Backout

Even with careful planning, things can go wrong-so you need a clear recovery plan. This module focuses on how to quickly roll back changes, restore a stable state, and reduce impact on users. It’s about being prepared to respond with a clear and confident plan when something doesn’t work as expected in production.

This module covers:

  • Backing out changes from production / main
  • Reverting individual commits vs. reverting an entire merge request
  • Cherry-picking known-good changes onto a recovery branch
  • Deleting or removing deployed extensions safely
  • Recovering from failed deployments
  • Understanding rollback options and their limitations
  • When to redeploy a previous version vs. when to fix forward

Suggested reading and viewing:

  • Rolling Back Changes
  • Backing Out VB Studio Changes from Production [Coming Soon]
  • Using Git Revert and Cherry-Pick Options [Coming Soon]

Conclusion

Think of this learning path as your guide for managing VB Studio extensions safely from start to finish. Start with the basics, get comfortable with branching (if needed), and learn how to move changes properly-once you’ve got those down, the more complex stuff becomes a lot less intimidating.