Our integration tests take a long time to run during CI. This is largely (but not exclusively) on account of the fact that they rebuild all images, one at a time, and load them into a KinD cluster before actually running the tests.
If we push candidate images to a registry as they are built, often concurrently, by preceding steps in the CI process, those images will not need to be rebuilt before the integration tests.
We wouldn't want to use a public registry for this purpose because we'd clutter it with unstable images. We could, however, deploy a private registry within our cluster and use it for this purpose.
My best guess is this will cut the time to execute CI tests by at least 50%.
Our integration tests take a long time to run during CI. This is largely (but not exclusively) on account of the fact that they rebuild all images, one at a time, and load them into a KinD cluster before actually running the tests.
If we push candidate images to a registry as they are built, often concurrently, by preceding steps in the CI process, those images will not need to be rebuilt before the integration tests.
We wouldn't want to use a public registry for this purpose because we'd clutter it with unstable images. We could, however, deploy a private registry within our cluster and use it for this purpose.
My best guess is this will cut the time to execute CI tests by at least 50%.