1️⃣ 𝗖𝗜/𝗖𝗗 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲
One of the biggest misconceptions is: “VB Studio deployments always need CI/CD pipelines.” It is no longer true, especially for extensions.

VB Studio supports direct deployment without CI/CD pipelines In your workspace, go to: Publish → (…) → Settings → Build and Publish
You will see a checkbox called: Enable CI/CD Pipeline
This checkbox decides how Publish behaves.

𝗪𝗵𝗲𝗻 𝗖𝗜/𝗖𝗗 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 𝗶𝘀 𝗘𝗡𝗔𝗕𝗟𝗘𝗗
When you click Publish. Your changes are merged into the Target Branch
VB Studio triggers a CI/CD pipeline (that builds the extension, packages it, deploys it)

𝗪𝗵𝗲𝗻 𝗖𝗜/𝗖𝗗 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 𝗶𝘀 𝗗𝗜𝗦𝗔𝗕𝗟𝗘𝗗 (𝗱𝗲𝗳𝗮𝘂𝗹𝘁 & 𝗿𝗲𝗰𝗼𝗺𝗺𝗲𝗻𝗱𝗲𝗱)
When this checkbox is disabled: Publish merges changes into the Target Branch
– Deployment happens directly
– No CI/CD pipeline is triggered
The result: Faster deployments, Fewer moving parts, Less operational overhead
👉 This is the recommended approach by the Oracle product team for extensions

Important: this is a BRANCH-level setting
The CI/CD pipeline setting applies to, the Target Branch and not an individual user or workspace
Example: If CI/CD is enabled for main → everyone publishing to main triggers pipelines
If CI/CD is disabled for main → everyone gets direct deployment

2️⃣ 𝗠𝗮𝗻𝗮𝗴𝗲 𝗘𝘅𝘁𝗲𝗻𝘀𝗶𝗼𝗻 𝗟𝗶𝗳𝗲𝗰𝘆𝗰𝗹𝗲 (𝗠𝗘𝗟)
MEL page provides a centralized, intuitive interface to manage extensions across environments. You can see:
– All OAuth-authenticated environments
– Extensions deployed in each environment
– Status, version, and deployment timestamps

Environments must be added using OAuth authentication to appear in MEL.
(Basic Auth environments will not show here.) Once added, each user must authenticate with their own credentials before performing deploy.

The 3 key actions in MEL: View Version Details, Deploy, Delete (Rollback)
Note: Delete removes the entire extension from that environment.
MEL does not automatically restore a previous version. You need to deploy the previous version to the target environment.

MEL also provides a toggle to: View extensions deployed only from your project Or view extensions deployed from all projects to the same environment
This helps identify cases where:
– Another project deployed an extension to the same environment
– Existing deployments were overridden
Earlier, this required support intervention.
Now it’s visible directly in the UI.