Add target to build images from supported-versions.yml file

[jsoriano]

Add mage targets intended to be used mostly by CI to prebuild
and push images used by integration and E2E tests. It leverages
existing docker compose scenarios, and build all the images in
the docker-compose.yml file associated to each
supported-versions.yml file.

To find the associated docker-compose.yml file, it follows similar
behaviour we have in other places, it starts descending directories
till it finds a directory with a docker-compose.yml file.

Usage example:

$ mage compose:buildSupportedVersions
2019/11/18 17:10:31 Found Elastic Beats dir at /home/jaime/gocode/src/github.com/elastic/beats
>> compose: Building docker images for supported versions
>> compose: Using compose file module/mysql/docker-compose.yml
>> compose: Building images for variant map[MYSQL_VARIANT:mysql MYSQL_VERSION:5.7.12]
>> compose: Building images for variant map[MYSQL_VARIANT:mysql MYSQL_VERSION:8.0.13]
>> compose: Building images for variant map[MYSQL_VARIANT:percona MYSQL_VERSION:5.7.24]
>> compose: Building images for variant map[MYSQL_VARIANT:percona MYSQL_VERSION:8.0.13-4]
>> compose: Building images for variant map[MYSQL_VARIANT:mariadb MYSQL_VERSION:10.2.23]
>> compose: Building images for variant map[MYSQL_VARIANT:mariadb MYSQL_VERSION:10.3.14]
>> compose: Building images for variant map[MYSQL_VARIANT:mariadb MYSQL_VERSION:10.4.4]
>> compose: OK

For push:

$ mage compose:pushSupportedVersions
2019/11/18 17:15:30 Found Elastic Beats dir at /home/jaime/gocode/src/github.com/elastic/beats
>> compose: Pushing docker images for supported versions
>> compose: Using compose file module/mysql/docker-compose.yml
>> compose: Pushing images for variant map[MYSQL_VARIANT:mysql MYSQL_VERSION:5.7.12]
...

Related to #14520 and #14355.

[mdelapenya]

Just started reviewing :)

Sent from GH.

[mdelapenya]

LGTM 👍

I'd see convenient to add a mageg target per service, so that it's possible to build one single service. wdyt?

[jsoriano]

I'd see convenient to add a mageg target per service, so that it's possible to build one single service. wdyt?

SUPPORTED_VERSIONS_FILE environment variable can be used to build only the variants defined in a specific file.

[mdelapenya]

I'd see convenient to add a mageg target per service, so that it's possible to build one single service. wdyt?

SUPPORTED_VERSIONS_FILE environment variable can be used to build only the variants defined in a specific file.

Wouldn't it be better for CI, instead of generating a file on the fly, having a target to do that? 🤔
Now I get it: the file already exists and the environment variable configures which one to build. Thanks!

[mdelapenya]

LGTM 👍

[jsoriano]

jenkins, test this again please

[jsoriano]

jenkins, test this again please

[jsoriano]

I don't think failures in CI are related, merging this.

[mdelapenya]

@jsoriano could we document how to run this command, and its main purpose?

[jsoriano]

@jsoriano could we document how to run this command, and its main purpose?

Yes, we have to revamp the developer guides, and we should include these targets in some explanation of the supported-versions.yml file. I don't think we have a place to document mage targets now.

In the meantime, do you need some clarification about these commands?