Bowrna commented on issue #19970: URL: https://github.com/apache/airflow/issues/19970#issuecomment-992752328
@potiuk I have checked the code in the existing breeze for build-image. **For CI image:** _prepare_ci_build:_ Prepares all variables needed by the CI build ( THE_IMAGE_TYPE, IMAGE_DESCRIPTION, AIRFLOW_EXTRAS etc). sanity_checks::go_to_airflow_sources Go to airflow path using dir pushd command Then fix group permission - get list of all files and filter out deleted files (not sure why it’s done) and change the permission of files Then do similarly for directory Pop the airflow path and set the permissions fixed as true _rebuild_ci_image_if_needed :_ This has more logic that includes checking multiple flags and depending on it pull images, computing md5sum for files, getting local_build_cache_hash, pulling the remote image cache hash and comparing it with local to find out if they are different. If yes then pull the remote docker image. for macOS-specific cases, do fix_ownership.sh After this do actual build_ci_image, manifest, update_all_md5 This is complex and involved many steps. What do you think is the best way for me to start working on this task? 1. Do I need to break this into more tasks and understand the existing code in more detail? 2. Can I take one small part of this entire build-image for ci and try writing it in python? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
