com.amazonaws.services.codebuild.model.ProjectCache Maven / Gradle / Ivy
/*
* Copyright 2014-2019 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with
* the License. A copy of the License is located at
*
* http://aws.amazon.com/apache2.0
*
* or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
* CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions
* and limitations under the License.
*/
package com.amazonaws.services.codebuild.model;
import java.io.Serializable;
import javax.annotation.Generated;
import com.amazonaws.protocol.StructuredPojo;
import com.amazonaws.protocol.ProtocolMarshaller;
/**
*
* Information about the cache for the build project.
*
*
* @see AWS API
* Documentation
*/
@Generated("com.amazonaws:aws-java-sdk-code-generator")
public class ProjectCache implements Serializable, Cloneable, StructuredPojo {
/**
*
* 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.
*
*
*
*/
private String type;
/**
*
* Information about the cache location:
*
*
* -
*
* NO_CACHE or LOCAL: This value is ignored.
*
*
* -
*
* S3: This is the S3 bucket name/prefix.
*
*
*
*/
private String location;
/**
*
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at the
* same time.
*
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does not use a Git
* repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for projects
* that build or pull large Docker images. It can prevent the performance hit that would be caused by pulling large
* Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a good
* choice if your build scenario does not match one that works well with 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 overriden
* if a source item has the same name. Directories are specified using cache paths in the buildspec file.
*
*
*
*
*
*/
private java.util.List modes;
/**
*
* 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.
*
*
*
*
* @param type
* 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.
*
*
* @see CacheType
*/
public void setType(String type) {
this.type = type;
}
/**
*
* 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.
*
*
*
*
* @return 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.
*
*
* @see CacheType
*/
public String getType() {
return this.type;
}
/**
*
* 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.
*
*
*
*
* @param type
* 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.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see CacheType
*/
public ProjectCache withType(String type) {
setType(type);
return this;
}
/**
*
* 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.
*
*
*
*
* @param type
* 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.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see CacheType
*/
public ProjectCache withType(CacheType type) {
this.type = type.toString();
return this;
}
/**
*
* Information about the cache location:
*
*
* -
*
* NO_CACHE or LOCAL: This value is ignored.
*
*
* -
*
* S3: This is the S3 bucket name/prefix.
*
*
*
*
* @param location
* Information about the cache location:
*
* -
*
* NO_CACHE or LOCAL: This value is ignored.
*
*
* -
*
* S3: This is the S3 bucket name/prefix.
*
*
*/
public void setLocation(String location) {
this.location = location;
}
/**
*
* Information about the cache location:
*
*
* -
*
* NO_CACHE or LOCAL: This value is ignored.
*
*
* -
*
* S3: This is the S3 bucket name/prefix.
*
*
*
*
* @return Information about the cache location:
*
* -
*
* NO_CACHE or LOCAL: This value is ignored.
*
*
* -
*
* S3: This is the S3 bucket name/prefix.
*
*
*/
public String getLocation() {
return this.location;
}
/**
*
* Information about the cache location:
*
*
* -
*
* NO_CACHE or LOCAL: This value is ignored.
*
*
* -
*
* S3: This is the S3 bucket name/prefix.
*
*
*
*
* @param location
* Information about the cache location:
*
* -
*
* NO_CACHE or LOCAL: This value is ignored.
*
*
* -
*
* S3: This is the S3 bucket name/prefix.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public ProjectCache withLocation(String location) {
setLocation(location);
return this;
}
/**
*
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at the
* same time.
*
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does not use a Git
* repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for projects
* that build or pull large Docker images. It can prevent the performance hit that would be caused by pulling large
* Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a good
* choice if your build scenario does not match one that works well with 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 overriden
* if a source item has the same name. Directories are specified using cache paths in the buildspec file.
*
*
*
*
*
*
* @return If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at
* the same time.
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does
* not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is
* ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for
* projects that build or pull large Docker images. It can prevent the performance hit that would be caused
* by pulling large Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a
* good choice if your build scenario does not match one that works well with 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
* overriden if a source item has the same name. Directories are specified using cache paths in the
* buildspec file.
*
*
*
*
* @see CacheMode
*/
public java.util.List getModes() {
return modes;
}
/**
*
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at the
* same time.
*
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does not use a Git
* repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for projects
* that build or pull large Docker images. It can prevent the performance hit that would be caused by pulling large
* Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a good
* choice if your build scenario does not match one that works well with 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 overriden
* if a source item has the same name. Directories are specified using cache paths in the buildspec file.
*
*
*
*
*
*
* @param modes
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at
* the same time.
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does
* not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is
* ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for
* projects that build or pull large Docker images. It can prevent the performance hit that would be caused
* by pulling large Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a
* good choice if your build scenario does not match one that works well with 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
* overriden if a source item has the same name. Directories are specified using cache paths in the buildspec
* file.
*
*
*
*
* @see CacheMode
*/
public void setModes(java.util.Collection modes) {
if (modes == null) {
this.modes = null;
return;
}
this.modes = new java.util.ArrayList(modes);
}
/**
*
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at the
* same time.
*
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does not use a Git
* repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for projects
* that build or pull large Docker images. It can prevent the performance hit that would be caused by pulling large
* Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a good
* choice if your build scenario does not match one that works well with 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 overriden
* if a source item has the same name. Directories are specified using cache paths in the buildspec file.
*
*
*
*
*
*
* NOTE: This method appends the values to the existing list (if any). Use
* {@link #setModes(java.util.Collection)} or {@link #withModes(java.util.Collection)} if you want to override the
* existing values.
*
*
* @param modes
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at
* the same time.
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does
* not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is
* ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for
* projects that build or pull large Docker images. It can prevent the performance hit that would be caused
* by pulling large Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a
* good choice if your build scenario does not match one that works well with 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
* overriden if a source item has the same name. Directories are specified using cache paths in the buildspec
* file.
*
*
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see CacheMode
*/
public ProjectCache withModes(String... modes) {
if (this.modes == null) {
setModes(new java.util.ArrayList(modes.length));
}
for (String ele : modes) {
this.modes.add(ele);
}
return this;
}
/**
*
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at the
* same time.
*
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does not use a Git
* repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for projects
* that build or pull large Docker images. It can prevent the performance hit that would be caused by pulling large
* Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a good
* choice if your build scenario does not match one that works well with 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 overriden
* if a source item has the same name. Directories are specified using cache paths in the buildspec file.
*
*
*
*
*
*
* @param modes
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at
* the same time.
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does
* not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is
* ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for
* projects that build or pull large Docker images. It can prevent the performance hit that would be caused
* by pulling large Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a
* good choice if your build scenario does not match one that works well with 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
* overriden if a source item has the same name. Directories are specified using cache paths in the buildspec
* file.
*
*
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see CacheMode
*/
public ProjectCache withModes(java.util.Collection modes) {
setModes(modes);
return this;
}
/**
*
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at the
* same time.
*
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does not use a Git
* repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for projects
* that build or pull large Docker images. It can prevent the performance hit that would be caused by pulling large
* Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a good
* choice if your build scenario does not match one that works well with 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 overriden
* if a source item has the same name. Directories are specified using cache paths in the buildspec file.
*
*
*
*
*
*
* @param modes
* If you use a LOCAL cache, the local cache mode. You can use one or more local cache modes at
* the same time.
*
* -
*
* LOCAL_SOURCE_CACHE mode 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 your project does
* not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket) and you choose this option, then it is
* ignored.
*
*
* -
*
* LOCAL_DOCKER_LAYER_CACHE mode caches existing Docker layers. This mode is a good choice for
* projects that build or pull large Docker images. It can prevent the performance hit that would be caused
* by pulling large Docker images down from the network.
*
*
*
* -
*
* You can only use a Docker layer cache in the Linux enviornment.
*
*
* -
*
* The privileged flag must be set so that your project has the necessary Docker privileges.
*
*
* -
*
* You should consider the security implications before using a Docker layer cache.
*
*
*
*
*
*
* -
*
* LOCAL_CUSTOM_CACHE mode caches directories you specify in the buildspec file. This mode is a
* good choice if your build scenario does not match one that works well with 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
* overriden if a source item has the same name. Directories are specified using cache paths in the buildspec
* file.
*
*
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see CacheMode
*/
public ProjectCache withModes(CacheMode... modes) {
java.util.ArrayList modesCopy = new java.util.ArrayList(modes.length);
for (CacheMode value : modes) {
modesCopy.add(value.toString());
}
if (getModes() == null) {
setModes(modesCopy);
} else {
getModes().addAll(modesCopy);
}
return this;
}
/**
* Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be
* redacted from this string using a placeholder value.
*
* @return A string representation of this object.
*
* @see java.lang.Object#toString()
*/
@Override
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
if (getType() != null)
sb.append("Type: ").append(getType()).append(",");
if (getLocation() != null)
sb.append("Location: ").append(getLocation()).append(",");
if (getModes() != null)
sb.append("Modes: ").append(getModes());
sb.append("}");
return sb.toString();
}
@Override
public boolean equals(Object obj) {
if (this == obj)
return true;
if (obj == null)
return false;
if (obj instanceof ProjectCache == false)
return false;
ProjectCache other = (ProjectCache) obj;
if (other.getType() == null ^ this.getType() == null)
return false;
if (other.getType() != null && other.getType().equals(this.getType()) == false)
return false;
if (other.getLocation() == null ^ this.getLocation() == null)
return false;
if (other.getLocation() != null && other.getLocation().equals(this.getLocation()) == false)
return false;
if (other.getModes() == null ^ this.getModes() == null)
return false;
if (other.getModes() != null && other.getModes().equals(this.getModes()) == false)
return false;
return true;
}
@Override
public int hashCode() {
final int prime = 31;
int hashCode = 1;
hashCode = prime * hashCode + ((getType() == null) ? 0 : getType().hashCode());
hashCode = prime * hashCode + ((getLocation() == null) ? 0 : getLocation().hashCode());
hashCode = prime * hashCode + ((getModes() == null) ? 0 : getModes().hashCode());
return hashCode;
}
@Override
public ProjectCache clone() {
try {
return (ProjectCache) super.clone();
} catch (CloneNotSupportedException e) {
throw new IllegalStateException("Got a CloneNotSupportedException from Object.clone() " + "even though we're Cloneable!", e);
}
}
@com.amazonaws.annotation.SdkInternalApi
@Override
public void marshall(ProtocolMarshaller protocolMarshaller) {
com.amazonaws.services.codebuild.model.transform.ProjectCacheMarshaller.getInstance().marshall(this, protocolMarshaller);
}
}