8 Deploy and Manage Your Applications

By using an Oracle Deployment build step, you can deploy an application to an instance called a deployment target. You deploy extensions to Oracle Cloud Applications instances, visual applications to Visual Builder instances, or other build artifacts, like Java or Node.js applications, to instances running Oracle Java Cloud Service (JCS). 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 with user credentials that are authorized to deploy to the target Oracle Cloud Applications or Visual Builder instance. If your project owner hasn't provided these credentials, you'll be prompted for them each time you click Publish, and must enter them before you can continue.

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 jobs instead, so you aren't prompted for them each time the job runs.

See Configure the Deployment 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:

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.

  • You can delete an extension in an Oracle Cloud Applications instance in the current identity domain.

    However, if the extension is in another identity domain, you'll need to either use an Application Extension : Delete build step to perform this operation or use the Manage Extension Lifecycle page.

    The Manage Extension Lifecycle page provides a simpler interface where you can manage the application lifecycle operations for extensions without the need to create build jobs and pipelines. For more information, see Manage Your Published Extensions.