Deploy and Manage Your Applications

By using a Deploy build step, you can deploy an application to an instance called a deployment target. You deploy extensions to Oracle Cloud Applications instances and visual applications to Visual Builder instances. You can enable continuous delivery, a method for automatically deploying a build artifact to the target service, by enabling the Auto Start functionality in a pipeline that contains a deployment build step.

Note: Before you can publish an extension or visual application from the Designer, the pipeline’s deployment job must be configured to deploy to the target Oracle Cloud Applications or Visual Builder instance.

• If the deployment job uses OAuth (recommended), authorization must be provided for OAuth tokens to be created with the credentials of a user who has permissions to connect and deploy to the target instance. You won’t be able to publish without this authorization. It is recommended that you authorize your connection during initial job configuration—though you’ll be prompted to authorize missing or expired OAuth tokens when you click Publish.

• If your deployment job uses Basic authentication, credentials of a user who can connect and deploy to the target instance must be provided. If your project owner hasn’t provided these credentials, you’ll be prompted for them when you click Publish for the first time. If valid, the credentials will be permanently saved in the deployment job. If you don’t know the credentials, you’ll need to talk to your project owner or an administrator. Your administrator may choose to enter the credentials directly in the build job instead, so you aren’t prompted for them when you try to deploy your extension or visual app.

See Create a Deployment Build Job for extensions or Configure the Deployment Job for visual applications.

Application lifecycle operations for extensions and visual applications can be managed by using the options under their respective build step menus:

• Extensions can be packaged and deployed extensions can be deleted.

• Visual applications can be packaged, data can be imported from and exported to applications, deployed applications can be locked and unlocked, changes can be rolled back to a previous version, and deployed applications can be undeployed.

  See Lock, Unlock, or Roll Back a Deployed Visual Application for information about lock, unlock, and rollback operations.

  See Configure a Build Job to Import or Export Data from a Visual Application for information about importing data from and exporting data to visual applications.

For visual applications, some of these operations can also be managed from the activity menu in the Environments page’s Deployments tab:

• You can export data from, import data to, and undeploy a visual application that’s deployed to your current identity domain’s Visual Builder instance.

  However, if your visual application is in another identity domain, you’ll need to create and use the Visual Application : Export Data, Visual Application : Import Data, or Visual Application : Undeploy build steps to undeploy to perform these operations.

For extensions, some of these operations can be managed on the Manage Extension Lifecycle page:

• You can deploy an already published extension to a new Oracle Cloud Applications instance. See Manage Your Published Extensions in Extending Oracle Cloud Applications with Visual Builder Studio.

• You can delete an extension when no longer needed.

Tip: If you don’t need the extra functionality that CI/CD pipelines provide, you do have the option to deploy extensions and visual applications directly to their target instances, without the use of deployment jobs. To do this, you’d disable the CI/CD pipeline setting for the target branch that you’re merging your changes to. See Enable or Disable the CI/CD Pipeline for Publishing and Enable or Disable the CI/CD Pipeline for Deployments.