A small addition to the meta-data page #2477
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A clarification that emerged in a support ticket discussion. Having this explicitly in the docs might help someone down the line.
karensawrey
requested review from
mbelton-buildkite,
MelissaKaulfuss and
meiqimichelle
as code owners
github-actions
bot
added
the
pipelines
|
Preview URL: https://2477--bk-docs-preview.netlify.app |
| @@ -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). | |||
There was a problem hiding this comment.
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)?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A clarification that emerged in a support ticket discussion. Having this explicitly in the docs might help someone down the line.