Deploy to Test and Production Instances

If you're a developer who's fairly comfortable with Git and the development lifecycle, you'll probably want to set things up so that you have control of moving your extension from the development phase into test, and finally to production.
When a project is first created and configured, it's typically set up so that changes committed to the main branch automatically kick off a pipeline that packages up the extension and deploys it to whichever Oracle Cloud Applications instance was named as the project's Development instance. You can modify this pipeline so that your extensions are deployed to other non-production Oracle Cloud Applications instances as well, like a test pod or another Development environment. This involves the following steps:
  1. Create a VB Studio environment for each Oracle Cloud Applications instance to which you want to deploy.
  2. Create a deploy job for each instance you defined in step 1.
  3. Set up the pipeline to run the package and deploy jobs you created in step 2. In most cases you'll want to have this pipeline automatically triggered when anyone commits to main, but you have the option to run the pipeline manually. (As an individual developer working alone or with just a few others on a project, it's unlikely that this option would appeal to you, but it does exist.)

Note:

If your Oracle Cloud Applications instance is not in the same identity domain as your VB Studio instance, you can use OAuth tokens to access the instance. All you need to do is provide credentials of a user that can access the instance, when prompted. If needed, talk to your administrator to get Oracle Cloud Application credentials that you can use. See Create or Renew OAuth Tokens to Deploy Your Extension.
When you're ready to move your extension to production, the process is similar, with a few additional steps:
  1. Create a VB Studio environment for the Oracle Cloud Applications production instance.
  2. Create a new branch in your project's Git repo for changes that are ready for production. After creating this branch, any changes pushed to the main branch won't automatically be added to the production branch. Instead, you must create a merge request or manually push the changes to the production branch, as a means of protecting the branch against untested or unwanted additions.
  3. Create a production packaging build job, which generates an extension artifact that ready to deploy to the mainline.
  4. Create the production deployment build job, which deploys the artifact to the Oracle Cloud Application's production instance.
  5. Set up the production build pipeline.
Step-by-step instructions for both of these processes are available here:

Tip:

Just like you have the option to bypass the pipeline when initially publishing your extension, you can also bypass the pipeline when deploying it to other Oracle Cloud Applications instances. To do this, use the Manage Extension Lifecycle page.