User Story:

Slack notes from Andrea:

 
When running the OVE ISO job against the agent-installer-utils repo --> to use the new PR code
When running the OVE ISO job against another repo (ie, installer, dev-scripts) --> to use the latest (accepted) iso_builder code for that release branch

The solution here is to follow a similar approach previously adopted by the appliance:
In the agent-installer-utils CI repo a new image - called agent-ove-iso-builder - containing only the tools/iso_builder code will be built and promoted in the ocp namespace (in a similar fashion as the agent-preinstall-image-builder).
This image will never be used for OCP, but it will keep the latest src code version for each branch

A new AGENT_OVE_ISO_BUILDER_IMAGE dependency will be added to baremetalds-devscripts-setup step (like the APPLIANCE_IMAGE)
In the same step script, if the AGENT_E2E_TEST_BOOT_MODE == ISO_NO_REGISTRY then the AGENT_OVE_ISO_BUILDER_IMAGE env var will be added to the config_root.sh

In dev-scripts create_agent_iso_no_registry, instead of checking out the code from git, it will be then extracted from AGENT_OVE_ISO_BUILDER_IMAGE

In this way we'll be sure that each branch job will always use the most updated - and related - iso-builder code.
 
https://redhat-internal.slack.com/archives/C07S2QH1VL7/p1760101001428709