Extract basic tests to separate workflow#38206
Merged
Merged
Conversation
ceab36d to
0901abd
Compare
Similarly as with other extractions - this one will extract all the tests that need just basic "build-info" dependencies to a separate workflow. This will allow to keep the ci.yml better organised - eventually consisting of just calling other workflows. It also assigns all the basic checks to be run on the public ASF runners. There is no point in using our self-hosted runners to run those tests, they are usually pretty fast even on a small public runner (and they are not on a critical path for elapsed time of the workflow run - no other tests depend on them).
0901abd to
fa42a8e
Compare
Member
Author
eladkal
approved these changes
Mar 16, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Similarly as with other extractions - this one will extract all the tests that need just basic "build-info" dependencies to a separate workflow. This will allow to keep the ci.yml better organised - eventually consisting of just calling other workflows.
It also assigns all the basic checks to be run on the public ASF runners. There is no point in using our self-hosted runners to run those tests, they are usually pretty fast even on a small public runner (and they are not on a critical path for elapsed time of the workflow run - no other tests depend on them).
^ 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 newsfragments.