Use current code, not published images, in ES integration tests

[yurishkuro]

jaeger/plugin/storage/integration/es_index_cleaner_test.go

Lines 35 to 36 in 3b9428e

	indexCleanerImage = "jaegertracing/jaeger-es-index-cleaner:latest"
	rolloverImage = "jaegertracing/jaeger-es-rollover:latest"

This test is invoked from scripts/es-integration-test.sh.

Here the test is using :latest build of the helper containers. This is what happens in the CI:

=== RUN   TestIndexCleaner_doNotFailOnEmptyStorage
Unable to find image 'jaegertracing/jaeger-es-index-cleaner:latest' locally
latest: Pulling from jaegertracing/jaeger-es-index-cleaner
Digest: sha256:9020812f290230b65e2ada3dcab193c419b7f8bb29435bab045f8802482d0004
Status: Downloaded newer image for jaegertracing/jaeger-es-index-cleaner:latest

In other words, instead of testing the current code (which could've been changed in the PR under test), we are using a published image built from the main branch.

We need to refactor this test. Since these helper containers are not used in any other CI workflows, it's good to test them in this workflow. We need to build the containers locally similar to this other script:

jaeger/scripts/build-upload-docker-images.sh

Lines 61 to 62 in 3b9428e

	bash scripts/build-upload-a-docker-image.sh ${LOCAL_FLAG} -b -c jaeger-es-index-cleaner -d cmd/es-index-cleaner -p "${platforms}" -t release
	bash scripts/build-upload-a-docker-image.sh ${LOCAL_FLAG} -b -c jaeger-es-rollover -d cmd/es-rollover -p "${platforms}" -t release

And then use a specific tag (not :latest) when executing the test.

[hellspawn679]

@yurishkuro, can you give a reference to how containers are built locally and tested in other scripts?

[yurishkuro]

I already have a link in the description