Oracle Cloud Infrastructure Documentation

Deliver Artifacts Stage

The Deliver Artifacts stage maps the build outputs from the Managed Build stage with the version to deliver to a DevOps artifact resource, and then to the Oracle Cloud Infrastructure (OCI) code repository.

The build process generates artifacts, which are software applications or packages that you deploy to target deployment environments. The artifact produced by the Managed Build stage has to be stored in an artifact repository for deployment. DevOps supports artifacts stored in OCI Container Registry and OCI Artifact Registry repositories. The artifacts can be either container images (OCIR) or generic (universal) file types.

Configuring Delivered Artifact Version

You have to create a DevOps artifact to point to the repository location containing the build output.

The version of the software package that is delivered to the OCI code repository is defined by a parameter in the artifact uniform resource identifier (URI). This parameter matches the build specification exported variable or the build pipeline parameter name.

After you create a DevOps artifact referencing either the Container Registry repository or the Artifact Registry repository location, note the artifact location as given in the following example:
  • Name: node-express-getting-started container
  • Type: Container image repository
  • Path: iad.ocir.io/TENANCY-NAMESPACE/node-express-getting-started
  • Replace parameters: Yes

    Parameters are replaced at runtime with the values provided during the build.

For the artifact version that is delivered during the build run, assign the Managed Build stage exportedVariables: value to the artifact (image or package) tag. For example, in the build_spec.yaml file, if the exportedVariables: value is BUILDRUN_HASH, then you have to edit the DevOps artifact path to add the tag value as a parameter name as follows:

Path: iad.ocir.io/TENANCY-NAMESPACE/node-express-getting-started:${BUILDRUN_HASH}