Struct ProjectCache

pub struct ProjectCache {
    pub location: Option<String>,
    pub modes: Option<Vec<String>>,
    pub type_: String,
}

Information about the cache for the build project.

Fields

location: Option<String>

Information about the cache location:

• NO_CACHE or LOCAL: This value is ignored.

• S3: This is the S3 bucket name/prefix.

modes: Option<Vec<String>>

An array of strings that specify the local cache modes. You can use one or more local cache modes at the same time. This is only used for LOCAL cache types.

Possible values are:

LOCALSOURCECACHE

Caches Git metadata for primary and secondary sources. After the cache is created, subsequent builds pull only the change between commits. This mode is a good choice for projects with a clean working directory and a source that is a large Git repository. If you choose this option and your project does not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket), the option is ignored.

LOCALDOCKERLAYERCACHE

Caches existing Docker layers. This mode is a good choice for projects that build or pull large Docker images. It can prevent the performance issues caused by pulling large Docker images down from the network.

• You can use a Docker layer cache in the Linux environment only.

• The privileged flag must be set so that your project has the required Docker permissions.

• You should consider the security implications before you use a Docker layer cache.

LOCALCUSTOM_CACHE

Caches directories you specify in the buildspec file. This mode is a good choice if your build scenario is not suited to one of the other three local cache modes. If you use a custom cache:

• Only directories can be specified for caching. You cannot specify individual files.

• Symlinks are used to reference cached directories.

• Cached directories are linked to your build before it downloads its project sources. Cached items are overridden if a source item has the same name. Directories are specified using cache paths in the buildspec file.

type_: String

The type of cache used by the build project. Valid values include:

• NO_CACHE: The build project does not use any cache.

• S3: The build project reads and writes from and to S3.

• LOCAL: The build project stores a cache locally on a build host that is only available to that build host.

Trait Implementations

impl Clone for ProjectCache

fn clone(&self) -> ProjectCache

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ProjectCache

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for ProjectCache

fn default() -> ProjectCache

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for ProjectCache

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for ProjectCache

fn eq(&self, other: &ProjectCache) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for ProjectCache

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for ProjectCache