Managed Build Stage
Managed Build stage builds and tests your software with a fast and scalable Oracle Cloud Infrastructure (OCI) DevOps service managed build runner that runs build instructions.
The build runner shape can be customized or set to the default value. A shape is a template that determines the number of CPUs, amount of memory, and other resources allocated to a newly created instance. You are charged for using the compute shape (OCPU and memory) during the build run. The default build runner shape comprising of 2 OCPU and 8GB memory is the quick start option with minimal provisioning delay whereas the customization takes longer to provision.
OCI DevOps provides Oracle Linux 7 as the base container image for the build and provides other runtimes such as Java, Git, and Apache Maven. For the entire list of runtimes provided by DevOps, see Build Runner Runtime Details. To build high-performance Java applications, you can use Oracle GraalVM in the build pipeline. For more information, see Using Oracle GraalVM in DevOps Build Pipelines.
In the DevOps service, you can connect to external code repositories such as GitHub, GitLab, Bitbucket Cloud, Visual Builder Studio, Bitbucket Server, and GitLab Server. For more information, see Creating External Connections.
Accessing Private Virtual Network
You can access self-hosted repositories (GitLab Server and Bitbucket Server) with private IP from the Managed Build stage. With the private access configuration, you can write commands in the build specification file to access the private endpoints in your Virtual Cloud Network (VCN). During the build, the service-managed build runner facilitates the connection from the build stage to your tenancy subnet. Using FastConnect or other IPSec VPN peering solutions, you can also create a connection to access your on-premises code repository from an OCI DevOps build runner.
Build runner instance is considered as a private instance in your VCN during the network setup. Using only an internet gateway doesn't allow egress to the internet from a private instance. Therefore, the VCN must have a Network Address Translation (NAT) gateway or service gateway with routing rules to forward traffic configured in the route table for the private access configuration to succeed in the Managed Build stage. The subnet that you select while configuring the private access must be region-specific as availability domain-specific subnet isn't supported. The subnet must have at least one IP address for connecting the build runner during the build execution. For troubleshooting, see Configuring Private Connection.