Step 1: Decide whether to use the free VM build executor
Required step: Decide whether to use the free build executor or an OCI account before you create the VB Studio instance. If you change your mind later, you can switch between the two, but you may have to manually migrate some of the data.
To package and deploy the applications you configure, VB Studio uses continuous integration and continuous delivery (CI/CD) build jobs. To run those builds, VB Studio can use either the free build executor or your own OCI account.
To help you decide, OCI Resources in VB Studio provides a comprehensive comparison, but here's a quick primer with links to the required setup for each option:
| Option | Description | Where to Get More Details |
|---|---|---|
| Free VM build executor |
VB Studio comes preconfigured with one OCI Compute VM to run builds. |
See VB Studio's Free VM Build Executor to learn more about the capabilities of the free VM build executor. |
| Your OCI account |
Use your own OCI account so you can add more build executors to reduce the wait time for your organization's members, create custom build executor templates, or use advanced features (such as use your own VCN or use a different VM shape). In addition, your build artifacts are stored in OCI Object Storage buckets, and you have the ability to increase storage space when needed. |
See Create a VB Studio Instance in Your Oracle Cloud Account. (You can also connect it later, as well.) |
If you're using the free build executor to deploy visual applications, you must manually authorize the VB Studio instance to access Visual Builder instances connected to your OCI account. Without this authorization, your users won't be able to create environments with a Visual Builder instance to deploy their visual applications. See Authorize VB Studio to Access Visual Builder and Integration Instances for the steps to complete this authorization.