getDockerBuildTask, is available for building a docker image for any given module. Behind the scene, it will generate a task which will run the build of a docker image in a specific folder. The goal is to make sure that we have an isolated context which helps with incrementality. All files that need to be present in the docker image will need to be copy into this folder. The generate method takes 2 arguments:
foois given as an image name, the image
airbyte/foowill be created
getDockerBuildTaskis declared in the rootProject
Dockerfile, generating the docker image is done in the following way:
build/docker/binfirst. The need to happen after the
copyDockertask clean up the
build/dockerfolder as a first step.
generate-dockerallows to build all the docker images.
.envfile to make sure that the latest version align with the version in the PR
masterbranch in the PR and make sure that the build is working right before merging.
.bumpversion.cfg. For each and every version you want to build with, the docker image will need to be manually tag and push until the PR is merge. The reason is that the build has a check to know if all the potential docker images are present in the docker repository. It is done the following way:
docker imagesor the docker desktop UI.