OCI DevOps-Build Pipelines and Code Repositories for CI

This article introduces Build Pipelines and Code Repositories in OCI DevOps (released on October 26th 2021) — complementing the Artifact Registry and Deployment Pipelines that were first launched in July of 2021 and that I discussed in this article.

Build [ing software] is an apparently clear indication of a specific process. With a clear result. Or is it? Build is typically an automated activity that is triggered sometimes manually but usually automatically by specific changes in a code repository. A commit or (more commonly) a pull request for a branch or the creation of a release tag will start a process we call the build process. What exactly the build process will do varies. Common elements though are:

• gather resources that are required for the process — from code repositories, library repositories (NPM, Maven, PyPI), container (image) registries
• validate digital signatures for sources and artifacts
• automated source code inspection and improvement such as linting and static code analysis
• transpilation
• compilation
• automated (unit) tests (tests that do not require deployment)
• creation of [optimized, minimized] deployable artifacts — such as container image or JAR, ZIP, Wheel, native binary (for example with GraalVM)
• validate/sign artifacts
• store artifact in a artifact repository — such…