Deploy Build Artifacts to Oracle Cloud Services

You can configure an Oracle Deploy build step to deploy your project's build artifacts like Java and Node.js applications to Oracle Cloud Services, including Oracle Java Cloud Service (JCS).

Before you can create a build step for deployment, you must first create an environment and then add the JCS instance to it. This instance will be used for your deployment target. If you don't add it in the Environments page, you won't be able to select it in the build step. See Set Up an Environment for information about creating an environment and adding instances to it.

Today, more and more customers are securing their resources and Oracle Cloud Services, such as JCS, behind private VCNs. If you already run Oracle Cloud services in your private VCN and plan to use VB Studio to deploy to those services, you should configure your private VCN so your services and these VMs are in the same VCN. VM build executors need to access VB Studio and VB Studio needs to access the VM build executors. That access is done through a public subnet that needs to be configured. See Allow VM Build Executors to Access A Private Subnet's Resources.

You can either add a build step that deploys the build artifact(s) to the job that creates and packages the artifact(s) or you can create a separate job for each task. If you use separate jobs, you can create a pipeline that begins with a job that builds and packages the application, followed by a job that deploys the build artifact(s) to the desired target environment. Using pipelines allows you the flexibility to add testing and other tasks to the flow.