potiuk opened a new issue #21103: URL: https://github.com/apache/airflow/issues/21103
In many breeze commands, we want to check if the image is "fresh" - i.e. whether the changes in the current sources are much different from the ones we had when the last time we run "breeze-build-image` (CI image only). In case we find that there were changes to important files (using hashes stored in .build) we should: 1) ask the user if it is ok to rebuild the image (timing out after 4 seconds) 2) if the user answered "yes" make sure that the code of the user is rebased and if not - warn the user that it might take a lot of time and only proceed if the user agrees to it 3) after successful rebuild we should store "hashes" of all the important files in .build - this way we will know, next time when those file change, that the last build was done when those files were different. -- 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]
