Kightly pipeline failures in deploy_feature_a and deploy_feature_b due to OOD_IMAGE_ID variable conflict

Summary

The deploy_feature_a and deploy_feature_b pipeline jobs merged in !246 (merged) were failing in production due to a variable conflict in deploy_ood.

Root Cause

Two issues combined to cause the pipeline failures:

1. Variable conflict in deploy_ood: The script was manually reassigning OOD_IMAGE_ID using BUILT_OOD_IMAGE_ID as a fallback — but the runner already provides this value correctly.

2. Redundant rule condition: Both deploy jobs were gated on $BUILT_OOD_IMAGE_ID in the rules condition — but BUILT_OOD_IMAGE_ID is only an intermediate value used to set OOD_IMAGE_ID, and it's OOD_IMAGE_ID that actually gets used in the deploy jobs. Forcing BUILT_OOD_IMAGE_ID to be a pipeline variable was unnecessary

Linked MRs

• !239 — Original implementation of deploy_feature_a and deploy_feature_b
• !246 (merged) — Merged implementation improvements (pipeline ownership + fail on non-200)
• !249 (merged) - Fix for variable conflict