Deploy an Extension to a Oracle Cloud Applications Development Instance

When a project is created for you through the Edit Page in Visual Builder Studio workflow in an Oracle Cloud Application, several artifacts are created for you:

• A Git repository that contains the extension’s source code

• A Development environment that points to the development instance where your base Oracle Cloud Application is running

• Default build jobs that package and deploy the extension’s artifact to your development environment, along with a pipeline to run the build sequence. While these build jobs and pipelines are automatically created for you, whether they are enabled or disabled depends on your extension’s CI/CD Pipeline setting.

• A private workspace in which you can edit the extension in the Designer.

See What Project Artifacts Are Created? in Administering Visual Builder Studio.

Deployment from Remote Branch to Any Target Environment

In an Advanced Mode workspace, you can deploy a VB Extension from a remote repository branch directly to a supported target environment. For example, you can deploy a release branch to QA, UAT, or Production without first deploying it to the workspace environment and promoting it through Manage Extension Lifecycle.

To deploy an extension:

1. Open the Deploy dialog.
2. In Remote Branch, select the branch containing the extension changes.
3. In Target Environment, select an environment configured on the Environments or Manage Extension Lifecycle page.
4. If prompted, authorize access to the selected environment.
5. Click Deploy.

Note:

• Deployment to an environment other than the workspace environment is available only in Advanced Mode.
• In Express Mode, VB Studio deploys the remote target branch to the workspace-linked environment.
• OAuth environments are supported. Basic Authentication environments might appear in the list but cannot be selected for deployment.
• When deploying to an OAuth environment, you must authenticate with your own credentials, even if another user has already authenticated with that environment.
• VB Studio checks the selected environment’s status. Deployment is disabled if the environment is unavailable or its status cannot be determined.
• Deployment errors and compatibility warnings appear in the deployment response.