Split release image into per-python independent matrix of workflows #50320
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
A bit of an improvement in the release image workflow that I told @kaxil I will do:
There is a separate "composite" workflow now for each python version - this way when only one job fails for environmental reasons there are separate flows for different python version images - and the non-impacted images will be published without waiting for restarting of the single failing job. |
potiuk
force-pushed
the
separate-release-image-workflows-per-python
branch
from
02ee73c to
4aea073
Compare
Member
Author
|
Plus you can run only selected python versions as a small bonus |
potiuk
added
the
backport-to-v3-1-test
gopidesupavan
approved these changes
May 7, 2025
The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting.
potiuk
force-pushed
the
separate-release-image-workflows-per-python
branch
from
4aea073 to
ef42850
Compare
github-actions bot
pushed a commit
that referenced
this pull request
May 8, 2025
… workflows (#50320) The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting. (cherry picked from commit edec4c3) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Backport successfully created: v3-0-test
|
potiuk
added a commit
that referenced
this pull request
May 8, 2025
… workflows (#50320) (#50331) The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting. (cherry picked from commit edec4c3) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
ayush3singh
pushed a commit
to ayush3singh/airflow
that referenced
this pull request
May 8, 2025
…pache#50320) The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting.
kaxil
pushed a commit
that referenced
this pull request
Jun 3, 2025
… workflows (#50320) (#50331) The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job. It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting. (cherry picked from commit edec4c3) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The release workflow now will run separately for each image - which means that if both AMD / ARM images of the same python version have finished, the merge step for that Python version will run immediately rather than waiting for all Python versions to complete. This means that some images might be available a bit faster and that even if a single image releaase will fail for some reason, the other images will appear before we re-run that failed image job.
It also adds the possibility of overriding the python version images - we can now additionally filter which image versions should be run and option to disable automated "latest tag" setting.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.