Expose services to custom executor with $CI_JOB_SERVICES
Description
With #2885 (closed) we added the MVC for the custom executor, which allows the user to setup their own runner for environments that are not support natively,
We have the services keyword which can be useful when you have some kind of dependency on your job such as the database. If we expose this in the generic executor the users can set up their own services.
With the release of this feature, we are adding the CI_JOB_SERVICES
variable that exposes the job services in the custom executor
Proposal
Since we already expose all the information as env variables we should stick to this convention, but since there can be multiple services we should suffix them with an index for example:
CUSTOM_ENV_SERVICE_0_NAME
CUSTOM_ENV_SERVICE_0_ALIAS
CUSTOM_ENV_SERVICE_1_NAME
CUSTOM_ENV_SERVICE_1_ALIAS
...
Links to related issues and merge requests / references
Edited by Darren Eastman