# Sharing metadata with multiple pipelines

**URL:** <https://forum.buildkite.community/t/sharing-metadata-with-multiple-pipelines/2411>\
**Category:** General\
**Created:** [November 24, 2022, 3:18am UTC](https://forum.buildkite.community/t/sharing-metadata-with-multiple-pipelines/2411 "2022-11-24T03:18:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![benmc](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/benmc/32/1159_2.png) [@benmc](https://forum.buildkite.community/u/benmc)\
**Post date:** [November 24, 2022, 4:46am UTC](https://forum.buildkite.community/t/sharing-metadata-with-multiple-pipelines/2411/2 "2022-11-24T04:46:18Z")

</div>

Hey @lewis!

Thanks for your question!

A simialr question was asked previously and Jarryd provided the answer here: [How to make buildkite-agent meta-data get "key" optional - #3 by jarryd](https://forum.buildkite.community/t/how-to-make-buildkite-agent-meta-data-get-key-optional/2089/3)

TL;DR: it is possible by passing in the job UUID using the --job flag.

Hope that helps with your use case.

Cheers,  
Ben

---

_[View the full topic](https://forum.buildkite.community/t/sharing-metadata-with-multiple-pipelines/2411)._