[metricbeat][pythonIntegTest] is not resilience when connection issues

[v1v]

What

when running the integration tests if the docker environment cannot be pulled then the whole build fails.

Command

cd metricbeat
mage pythonIntegTest

Stacktrace

[2020-10-06T10:53:15.087Z] + mage pythonIntegTest
[2020-10-06T10:54:11.398Z] Generated fields.yml for metricbeat to /var/lib/jenkins/workspace/Beats_beats_master/src/github.com/elastic/beats/metricbeat/fields.yml
[2020-10-06T10:54:26.345Z] >> Building docker images
[2020-10-06T10:54:26.345Z] Building beat
[2020-10-06T10:54:58.493Z] Service 'beat' failed to build: The command '/bin/sh -c cd /usr/lib   && curl -sLo instantclient-basic-linux.zip https://download.oracle.com/otn_software/linux/instantclient/19600/instantclient-basic-linux.x64-19.6.0.0.0dbru.zip   && unzip instantclient-basic-linux.zip   && rm instantclient-basic-linux.zip' returned a non-zero code: 56
[2020-10-06T10:54:58.493Z] Error: running "docker-compose -p metricbeat_8_0_0_0dd24289fa-snapshot build --force-rm --pull" failed with exit code 1
script returned exit code 1

Actions

• Add retry in the mage goal, see https://github.com/elastic/beats/pull/21587 ✅
• Decouple the prepare docker environment from the test execution, then having a specific goal only for that particular prepare docker environment will allow the CI/CD systems to retry a few times

[botelastic[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.