buildkite · karensawrey · Sep 15, 2023 · MelissaKaulfuss · Sep 19, 2023
@@ -4,6 +4,8 @@ In this guide, we'll walk through using the Buildkite agent's [meta-data command
 
 Meta-data is intended to store data 1 kilobyte or less in size, to be used across steps. For example, you can tag a build with the software version it deploys so that you can later identify which build deployed a particular version. For anything over 1 kb use an [artifact](/docs/pipelines/artifacts) instead.
 
+Note that meta-data exists at the build level, so setting it in a job sets it for the build (and setting the same key in multiple jobs will result in the value from the last one to set it).
+
 
 ## Setting data
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,6 +4,8 @@ In this guide, we'll walk through using the Buildkite agent's [meta-data command

		Meta-data is intended to store data 1 kilobyte or less in size, to be used across steps. For example, you can tag a build with the software version it deploys so that you can later identify which build deployed a particular version. For anything over 1 kb use an [artifact](/docs/pipelines/artifacts) instead.

		Note that meta-data exists at the build level, so setting it in a job sets it for the build (and setting the same key in multiple jobs will result in the value from the last one to set it).
Copy link Contributor MelissaKaulfuss Sep 19, 2023 • edited Loading Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. Can I ask what this means: "Setting the same key in multiple jobs will result in the value from the last one to set it." Does this mean, if there's a key in the meta-data at the build level, and the value is being set inside multiple jobs (in that one build), that the final key/value pair that's stored in the metadata at the build level will be the one that was last set (in the last job)?


		## Setting data

Expand Down