What happened:
When using the Remote trigger / Remote join feature in Screwdriver, metadata defined in the upstream pipeline is automatically inherited by the downstream pipeline.
This inherited metadata behaves as if it were defined directly in the downstream pipeline, which can cause confusion.
Especially, downstream event cards display the inherited parameters same as own.
This behavior is inconsistent with the meta-cli functionality, which provides an --external option for explicitly referencing metadata from another pipeline.
Since the current inheritance is implicit, the expected behavior is unclear and may lead to unintended dependencies.
What you expected to happen:
Upstream pipeline metadata should not be implicitly inherited by the downstream pipeline.
Instead, downstream pipelines should explicitly retrieve upstream metadata by using the meta-cli --external option.
If necessary, users can explicitly set inherited values by using meta get --external followed by meta set, making metadata dependencies intentional and predictable.
How to reproduce it:
- Configure an upstream pipeline with metadata values (e.g., build parameters).
- Trigger a downstream pipeline using Remote trigger / Remote join.
- Observe that the downstream pipeline’s metadata includes values from the upstream pipeline.
- In the UI, event cards display upstream metadata as if it were configured by the downstream pipeline itself.
What happened:
When using the Remote trigger / Remote join feature in Screwdriver, metadata defined in the upstream pipeline is automatically inherited by the downstream pipeline.
This inherited metadata behaves as if it were defined directly in the downstream pipeline, which can cause confusion.
Especially, downstream event cards display the inherited parameters same as own.
This behavior is inconsistent with the meta-cli functionality, which provides an
--externaloption for explicitly referencing metadata from another pipeline.Since the current inheritance is implicit, the expected behavior is unclear and may lead to unintended dependencies.
What you expected to happen:
Upstream pipeline metadata should not be implicitly inherited by the downstream pipeline.
Instead, downstream pipelines should explicitly retrieve upstream metadata by using the meta-cli
--externaloption.If necessary, users can explicitly set inherited values by using meta get
--externalfollowed bymeta set, making metadata dependencies intentional and predictable.How to reproduce it: