OCI Resources in VB Studio
VB Studio uses your OCI resources to run builds that package and deploy your application, and to store build artifacts. As part of your VB Studio setup, you should decide if the built-in free account is sufficient, or if you want VB Studio to use your OCI tenancy to create Compute instances and Storage objects for CI/CD build jobs.
Review the differences between both options to decide if you need the additional resources that your OCI account provides:
- Built-in free account: The VB Studio instance comes preconfigured with a built-in free account that offers one OCI Compute VM to run builds. (Available in all regions in the OC1 realm and will be made available in select other realms, such as OC2, OC3, and OC4, in the future.)
- OCI account: If you're subscribed to OCI, you can use your own account's OCI Compute VMs to run builds. To use your own OCI Compute VMs, configure VB Studio to connect to your OCI account.
This table summarizes the differences between the built-in free account and your OCI account:
| Features | Built-In Free Account | Your OCI Account | What it means |
|---|---|---|---|
| Number of build executors |
1 |
Unlimited |
A VM executor can run only one build at a time. The more VM executors you have available, the more builds your organization's members can run at the same time. If members trigger multiple builds while VM executors are already running, they must wait until a build running on the VM executor is complete. If VB Studio is connected to your OCI account, you can add multiple VM executors to reduce the build wait time for your organization's members. |
| Storage for build artifacts | 50 GB | Unlimited |
When your organization's members run builds, VB Studio saves the generated build artifacts in its configured storage space. If you're using the built-in free account, the build artifacts are stored in a limited storage space. If you run out of storage space, builds that generate artifacts will fail. If this happens, you must either remove some artifacts from the storage, or switch to an OCI account. You can't increase the storage space allocated to your built-in free account. If VB Studio is connected to your OCI account, the artifacts are stored in OCI Object Storage buckets. You can always increase the storage space to store more artifacts. |
| VM shape | Fixed shape | Custom shapes, including shapes offered by OCI |
The built-in free account offers a fixed shape OCI Compute VM. If VB Studio is connected to your OCI account, you can choose any VM shape offered by OCI. To learn more about shapes, see VM Shapes. |
| VCN | VB Studio's default VCN | VB Studio's default VCN or your custom VCN | If VB Studio is connected to your OCI account, you can add VM executors in a custom VCN to access Oracle Cloud services that are running in the same VCN. |
| Wait time | 5 minutes (fixed) | Custom wait time | After running a build, a VM executor waits for some time to run any queued builds. If no builds run in the wait time period, the VM executor stops. If a build triggers after a VM executor has stopped, the VM executor takes some time to start before it could run the build.
If VB Studio is connected to your OCI account, you can customize the wait time for your VM executors. |
| Maven and NPM repositories | Not available | Available | If VB Studio is connected to your OCI account, your organization's members can use their projects' hosted Maven and NPM repositories to upload custom dependencies and binary files. |