Save Cache to GCS Step Settings

Updated 2 months ago by Michael Cretzman

This topic provides settings and permissions for the CI Save Cache to GCS step.

The Save Cache to GCS step preserves files and directories between builds.

In this topic:


The unique name for this step.


See Entity Identifier Reference.

GCP Connector

The Harness Connector for the GCP account where you want to save the cache.


GCS bucket name.


The key to identify the cache.

You can use the checksum macro to create a key that is based on a file’s checksum. For example:

myApp-{{ checksum filePath1 }}

Harness checks to see if the key exists and compares the checksum. If the checksum matches, then Harness does not save the cache. If the checksum is different, then Harness saves the cache.

Source Paths

A list of the files/folders to cache. Add each file/folder separately.

Archive Format

Select the archive format.

The default archive format is Tar.

Override Cache

Select this option if you want to override the cache if the key already exists.

By default, the Override cache option is set to True.

Run as User

Set the value to specify the user id for all processes in the pod, running in containers. See Set the security context for a pod.

Set container resources

Maximum resources limit values for the resources used by the container at runtime.

Limit Memory

Maximum memory that the container can use.

You can express memory as a plain integer or as a fixed-point number using one of these suffixes: G, M.

You can also use the power-of-two equivalents: Gi, Mi.

Limit CPU

See Resource units in Kubernetes.

Limit the number of cores that the container can use.

Limits for CPU resources are measured in cpu units.

Fractional requests are allowed. The expression 0.1 is equivalent to the expression 100m, that can be read as one hundred millicpu.


Timeout for the step. Once the timeout is reached, the step fails, and the Pipeline execution continues.

See Also

Please Provide Feedback