tokoko commented on issue #34495: URL: https://github.com/apache/airflow/issues/34495#issuecomment-1728452347
@hussein-awala thanks for the reply. The setup that I was thinking of consists of various team-specific dockerfiles (for workers and dag-processors) that might be scattered across multiple git repos. I understand that managing multiple releases is less than ideal, but my thought process was that in case of a single release, cd process for a single repository after building it's own docker image will have to somehow reach out to some central helm deployer pipeline that is aware of other teams' deployments as well. Additionally, these deployments will have to be somehow queued so as not to coincide with one another. I suppose that's also doable, but seemed more awkward to me rather than an alternative where each repository's pipeline has a clear ownership of it's own deployments and might not be aware of other's existence at all. -- 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]
