Reference documentation and code samples for the Grafeas V1 Client class Artifact.
Artifact describes a build product.
Generated from protobuf messagegrafeas.v1.Artifact
Namespace
Grafeas \ V1
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ checksum
string
Hash or checksum value of a binary, or Docker Registry 2.0 digest of a container.
↳ id
string
Artifact ID, if any; for container images, this will be a URL by digest likegcr.io/projectID/imagename@sha256:123456.
↳ names
array
Related artifact names. This may be the path to a binary or jar file, or in the case of a container build, the name used to push the container image to Google Container Registry, as presented todocker push. Note that a single Artifact ID can have multiple names, for example if two tags are applied to one image.
getChecksum
Hash or checksum value of a binary, or Docker Registry 2.0 digest of a
container.
Returns
Type
Description
string
setChecksum
Hash or checksum value of a binary, or Docker Registry 2.0 digest of a
container.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getId
Artifact ID, if any; for container images, this will be a URL by digest
likegcr.io/projectID/imagename@sha256:123456.
Returns
Type
Description
string
setId
Artifact ID, if any; for container images, this will be a URL by digest
likegcr.io/projectID/imagename@sha256:123456.
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getNames
Related artifact names. This may be the path to a binary or jar file, or in
the case of a container build, the name used to push the container image to
Google Container Registry, as presented todocker push. Note that a
single Artifact ID can have multiple names, for example if two tags are
applied to one image.
Related artifact names. This may be the path to a binary or jar file, or in
the case of a container build, the name used to push the container image to
Google Container Registry, as presented todocker push. Note that a
single Artifact ID can have multiple names, for example if two tags are
applied to one image.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Grafeas V1 Client - Class Artifact (1.2.2)\n\nVersion latestkeyboard_arrow_down\n\n- [1.2.2 (latest)](/php/docs/reference/grafeas/latest/V1.Artifact)\n- [1.2.1](/php/docs/reference/grafeas/1.2.1/V1.Artifact)\n- [1.1.3](/php/docs/reference/grafeas/1.1.3/V1.Artifact)\n- [1.0.0](/php/docs/reference/grafeas/1.0.0/V1.Artifact)\n- [0.10.3](/php/docs/reference/grafeas/0.10.3/V1.Artifact)\n- [0.9.0](/php/docs/reference/grafeas/0.9.0/V1.Artifact)\n- [0.8.3](/php/docs/reference/grafeas/0.8.3/V1.Artifact)\n- [0.7.1](/php/docs/reference/grafeas/0.7.1/V1.Artifact)\n- [0.6.0](/php/docs/reference/grafeas/0.6.0/V1.Artifact)\n- [0.5.0](/php/docs/reference/grafeas/0.5.0/V1.Artifact)\n- [0.4.4](/php/docs/reference/grafeas/0.4.4/V1.Artifact) \nReference documentation and code samples for the Grafeas V1 Client class Artifact.\n\nArtifact describes a build product.\n\nGenerated from protobuf message `grafeas.v1.Artifact`\n\nNamespace\n---------\n\nGrafeas \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getChecksum\n\nHash or checksum value of a binary, or Docker Registry 2.0 digest of a\ncontainer.\n\n### setChecksum\n\nHash or checksum value of a binary, or Docker Registry 2.0 digest of a\ncontainer.\n\n### getId\n\nArtifact ID, if any; for container images, this will be a URL by digest\nlike `gcr.io/projectID/imagename@sha256:123456`.\n\n### setId\n\nArtifact ID, if any; for container images, this will be a URL by digest\nlike `gcr.io/projectID/imagename@sha256:123456`.\n\n### getNames\n\nRelated artifact names. This may be the path to a binary or jar file, or in\nthe case of a container build, the name used to push the container image to\nGoogle Container Registry, as presented to `docker push`. Note that a\nsingle Artifact ID can have multiple names, for example if two tags are\napplied to one image.\n\n### setNames\n\nRelated artifact names. This may be the path to a binary or jar file, or in\nthe case of a container build, the name used to push the container image to\nGoogle Container Registry, as presented to `docker push`. Note that a\nsingle Artifact ID can have multiple names, for example if two tags are\napplied to one image."]]
