Deploy to Other DEV and TEST Instances Through CI/CD Pipelines

If you’ve followed this chapter to this point, you’ve configured VB Studio to deploy extensions to your primary Oracle Cloud Applications Development environment. This section explains how to set up other Oracle Cloud Application instances, such as DEV and TEST, where your team members may want to test their extensions before deploying to PROD.

This involves creating an environment for each instance you want to deploy to, as well as configuring jobs and pipelines to package up and deploy extensions to those target instances.

Tip: If you don’t need a CI/CD pipeline to deploy your extension, skip this section and use the Manage Extension Lifecycle page to deploy to additional instances. From this single page, you can add new environments for your DEV and TEST instances and deploy extensions to those instances without the need to create build jobs and pipelines.

Before you proceed, make sure that the Oracle Cloud Applications instances are up and running.

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: You can also select Deploy to move all previously published changes for your Oracle Cloud Application to a target Oracle Cloud Applications environment. This is particularly useful for restoring a previously published extension after a P2T, or if the extension was accidentally deleted from the target environment.

• 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.