The auto-build for rucio-fs fails as it depends on the rucio-clients image. There is a race condition and in cases where the rucio-clients image is not pushed before the rucio-fs images, the auto-build fails.
This PR resolves this issue by waiting for rucio-clients to finish uploading before rucio-fs starts building. For future, such race conditions can be handled by the parent parameter in the build config
fts-cron
Both the Dockerfiles's have been moved to python3. In addition, the default Dockerfile is renamed to Dockerfile_cpp. Build config for Dockerfile_cpp and Dockerfile_java has been added. The build config specifies two new features:
custom-tag config parameter: this can be used to append a custom tag to push images
custom names for Dockerfiles: the build config can be suppled the path to the Dockerfile as the first parameter in case the name of the Dockerfile is not Dockerfile
rucio-fs
The auto-build for
rucio-fsfails as it depends on the rucio-clients image. There is a race condition and in cases where therucio-clientsimage is not pushed before therucio-fsimages, the auto-build fails.This PR resolves this issue by waiting for rucio-clients to finish uploading before rucio-fs starts building. For future, such race conditions can be handled by the
parentparameter in the build configfts-cron
Both the Dockerfiles's have been moved to python3. In addition, the default Dockerfile is renamed to
Dockerfile_cpp. Build config forDockerfile_cppandDockerfile_javahas been added. The build config specifies two new features: