Access private resources in the Build stage from OCI DevOps service

August 2, 2022 | 2 minute read
Srikrishna Padmannagari
Principal Product Manager
Text Size 100%:

We’re excited to announce the general availability of private resource access from the Managed Build runner in the Oracle Cloud Infrastructure (OCI) DevOps continuous integration and delivery (CI/CD) service. This new feature enabled you to access private resources on OCI or on-premises (connected to an OCI tenancy) from the Build stage.

With this new feature, you have the following capabilities:

  • Create a tunnel or path to your private VCN so that resources like private code repos and Artifact Registry can be used in the Managed Build stages.

  • Connect to self-hosted Git repositories, such as a Bitbucket or GitLab server, in your private virtual cloud network (VCN). This capability enables you to adhere to your organization’s security and compliance requirements, providing you with more control over access to your intellectual property and reducing the risk of exposing your resources.

Enable private access capability from the Build runner

To enable private access, you need the necessary policies.

In the service’s Managed Build stage, create a private connection by selecting the VCN and the subnet under the Connect to your tenancy subnet section to establish a private connection. You can also choose one or more network security groups (NSGs) to control traffic.

A screenshot of the Add A Stage page, showing private resource access on the Configure tab.


If you’re new to Oracle Cloud Infrastructure, you can get started by creating your Oracle Cloud Free Tier account. For more information, refer to the documentation:

Srikrishna Padmannagari

Principal Product Manager

Previous Post

Fast-track your move to Oracle Cloud Infrastructure

Sheryl Sage | 3 min read

Next Post

Announcing IPv6 ULA and multiple prefix support

Shahreen Fredrich | 5 min read