From fab7250dab7d2a4e57a250f4307778fe57d2de80 Mon Sep 17 00:00:00 2001 From: Karen Sawrey Date: Fri, 15 Sep 2023 18:01:18 +0200 Subject: [PATCH] A small addition to the meta-data page A clarification that emerged in a support ticket discussion. Having this explicitly in the docs might help someone down the line. --- pages/pipelines/build_meta_data.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/pipelines/build_meta_data.md b/pages/pipelines/build_meta_data.md index 18b62b2928..b54f10ba91 100644 --- a/pages/pipelines/build_meta_data.md +++ b/pages/pipelines/build_meta_data.md @@ -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