OCI Resources in VB Studio

In VB Studio, you use continuous integration and continuous delivery (CI/CD) build jobs to package and deploy your application. To run builds, VB Studio requires access to your OCI resources, such as your OCI Compute virtual machines (VMs).

You can use OCI resources either from your VB Studio instance's built-in free account, Oracle Free Tier account, or your own OCI account.

  • Built-in free account: 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. The VB Studio instance comes pre-configured with a built-in free account that offers one OCI Compute VM to run builds.
  • Free Tier account: All OCI accounts have a set of resources that are free of charge for the life of the account. The free tier account offers free micro Compute VMs that your organization's members can use to run builds. To use the OCI Compute VMs, configure VB Studio to connect to the Free Tier account.
  • OCI account: If you're subscribed to OCI, you can use your own account's OCI Compute VMs to run builds. To use OCI Compute VM, configure VB Studio to connect to your OCI account.

This table summarizes the differences between the built-in free account, free tier account, and your OCI account:

Features Built-In Free Account Free Tier Account Your OCI Account What it means?
Number of build executors

1

2-4

Depending on the size of the boot volume and the number of OCPUs that you allocate to each Ampere A1 Compute instance, you can create up to four compute instances.

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 200 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 or the free tier 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 or free tier 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

Flex shape

Custom shapes, including shapes offered by OCI

The built-in free account offers a fixed shape OCI Compute VM.

The free tier account offers the fixed VM.Standard.E2.1.Micro micro shape as well as the flexible ARM-based VM.Standard.A1.Flex shape. Docker cannot be used with the VM.Standard.A1.Flex shape. See Flexible Shapes.

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 2 VCNs 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 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 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.