BuildArgs class
The set of arguments for Build. The set of arguments for Build.
Constructors
-
BuildArgs({Input<
Artifacts> ? artifacts, Input<Secrets> ? availableSecrets, Input<List< ? images, Input<String> >String> ? location, Input<String> ? logsBucket, Input<BuildOptions> ? options, Input<String> ? project, required Input<String> projectId, Input<String> ? queueTtl, Input<List< ? secrets, Input<Secret> >String> ? serviceAccount, Input<Source> ? source, required Input<List< steps, Input<BuildStep> >Map< ? substitutions, Input<String, String> >List< ? tags, Input<String> >String> ? timeout}) -
Creates a new BuildArgs.
artifactsArtifacts produced by the build that should be uploaded upon successful completion of all build steps.availableSecretsSecrets and secret environment variables.imagesA list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in theBuildresource's results field. If any of the images fail to be pushed, the build status is markedFAILURE.locationOptional.logsBucketCloud Storage bucket where logs should be written (see Bucket Name Requirements). Logs file names will be of the format${logs_bucket}/log-${build_id}.txt.optionsSpecial options for this build.projectOptional.projectIdRequired. ID of the project.queueTtlTTL in queue for this build. If provided and the build is enqueued longer than this value, the build will expire and the build status will beEXPIRED. The TTL starts ticking from create_time.secretsSecrets to decrypt using Cloud Key Management Service. Note: Secret Manager is the recommended technique for managing sensitive data with Cloud Build. Useavailable_secretsto configure builds to access secrets from Secret Manager. For instructions, see: https://cloud.google.com/cloud-build/docs/securing-builds/use-secretsserviceAccountIAM service account whose credentials will be used at build runtime. Must be of the formatprojects/{PROJECT_ID}/serviceAccounts/{ACCOUNT}. ACCOUNT can be email address or uniqueId of the service account.sourceThe location of the source files to build.stepsThe operations to be performed on the workspace.substitutionsSubstitutions data forBuildresource.tagsTags for annotation of aBuild. These are not docker tags.timeoutAmount of time that this build should be allowed to run, to second granularity. If this amount of time elapses, work on the build will cease and the build status will beTIMEOUT.timeoutstarts ticking fromstartTime. Default time is 60 minutes.const -
BuildArgs.fromMap(Map<
String, dynamic> map) -
factory
Properties
-
artifacts
→ Input<
Artifacts> ? -
Artifacts produced by the build that should be uploaded upon successful completion of all build steps.
final
-
availableSecrets
→ Input<
Secrets> ? -
Secrets and secret environment variables.
final
- hashCode → int
-
The hash code for this object.
no setterinherited
-
images
→ Input<
List< ?String> > -
A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the
Buildresource's results field. If any of the images fail to be pushed, the build status is markedFAILURE.final -
location
→ Input<
String> ? -
final
-
logsBucket
→ Input<
String> ? -
Cloud Storage bucket where logs should be written (see Bucket Name Requirements). Logs file names will be of the format
${logs_bucket}/log-${build_id}.txt.final -
options
→ Input<
BuildOptions> ? -
Special options for this build.
final
-
project
→ Input<
String> ? -
final
-
projectId
→ Input<
String> -
Required. ID of the project.
final
-
queueTtl
→ Input<
String> ? -
TTL in queue for this build. If provided and the build is enqueued longer than this value, the build will expire and the build status will be
EXPIRED. The TTL starts ticking from create_time.final - runtimeType → Type
-
A representation of the runtime type of the object.
no setterinherited
-
secrets
→ Input<
List< ?Secret> > -
Secrets to decrypt using Cloud Key Management Service. Note: Secret Manager is the recommended technique for managing sensitive data with Cloud Build. Use
available_secretsto configure builds to access secrets from Secret Manager. For instructions, see: https://cloud.google.com/cloud-build/docs/securing-builds/use-secretsfinal -
serviceAccount
→ Input<
String> ? -
IAM service account whose credentials will be used at build runtime. Must be of the format
projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT}. ACCOUNT can be email address or uniqueId of the service account.final -
source
→ Input<
Source> ? -
The location of the source files to build.
final
-
steps
→ Input<
List< BuildStep> > -
The operations to be performed on the workspace.
final
-
substitutions
→ Input<
Map< ?String, String> > -
Substitutions data for
Buildresource.final -
Tags for annotation of a
Build. These are not docker tags.final -
timeout
→ Input<
String> ? -
Amount of time that this build should be allowed to run, to second granularity. If this amount of time elapses, work on the build will cease and the build status will be
TIMEOUT.timeoutstarts ticking fromstartTime. Default time is 60 minutes.final
Methods
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a nonexistent method or property is accessed.
inherited
-
toMap(
) → Map< String, dynamic> -
toString(
) → String -
A string representation of this object.
inherited
Operators
-
operator ==(
Object other) → bool -
The equality operator.
inherited