Closed juanjosevazquezgil closed 4 months ago
At the moment we are only handling services instead of adding an extra input to specify what kind of registry ( e.g. services, charts, runners...)
As in the following example code:
registryBasePaths.services[dispatch.type] // hardcoding services key
Motivation
We need to define the following new requisites for our workflow:
DOCKER_REGISTRIES_BASE_PATHS
, will be created. It will be used to create the full URL of the image repository we want to dispatch or where we want to upload the freshly built image. It will be constructed as follows:var.DOCKER_REGISTRY_[RELEASES or SNAPSHOTS]
/DOCKER_REGISTRIES_BASE_PATHS[services][releases or snapshots]
/github.repository
. It will be used only when dealing with the default image repository name (that is, the Github repo name) and only for one of the default docker registries. The data contained in the variable will be in YAML format, like this:Acceptance criteria