Add CI_TEMPLATE_REGISTRY_HOST to predefined CI variables
What does this MR do and why?
Related to issue #353815.
In those two MRs !91051 (merged) and !92722 (merged), we added TEMPLATE_REGISTRY_HOST to CI templates, so we can overwrite it by instance level CI variables.
And in this discussion !91051 (comment 1027332233), we found that we can move TEMPLATE_REGISTRY_HOST
to predefined CI variables, so we can overwrite it in JH side. So I rename TEMPLATE_REGISTRY_HOST
to CI_TEMPLATE_REGISTRY_HOST
and moved it to predefined CI variables.
/cc @prajnamas
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.