I am building inside a CI Pipeline. When using the Jib build with Maven and Google Cloud Build, there is a call to local Maven before the actual build is made on Google Cloud Build. The call looks like this:

mvn jib:_skaffold-fail-if-jib-out-of-date -Djib.requiredVersion=1.4.0 --projects wapi-app --also-make jib:_skaffold-files-v2 --quiet --batch-mode

This call causes all project dependencies to be downloaded, which takes approximately 4 minutes on our project.

Now that Jib has been called locally, Skaffold triggers Google Cloud Build. The Google Cloud Build is a new VM, so it again downloads the dependencies.

Any advice? This is unusable for any serious work in this state. Google Cloud Build is faster when downloading the dependencies, so I would be really happy to skip the first one.