Most of our jenkins jobs currently take an OCP_API_URL parameter to specify which cluster to run on.

For manual runs using a hive pool-based clusters, this is inconvenient, since it requires users to copy the URL from the slack message or the kubeconfig. It is also error-prone when dealing with multiple clusters, since the API URL has no indication which claim it belongs to.

AC:

The OCP_API_URL parameter accepts a claim name in addition to the full API URL

jenkins recognizes whether the provided value is a claim name and dynamically gets the URL from the hive cluster.

The translation from claim name to API URL is handled centrally in a library function, with minimal changes to the job jenkinsfiles

Optionally, the parameter is renamed to reflect the option to use URL or claim name