ci: run checks in CI#70
Draft
cagatay-y wants to merge 2 commits into
Draft
Conversation
The Dockerfile defines an image that contains the tools necessary to build the kernel and modules, and builds the appropriate version of the kernel to be used for CI. The workflow builds and pushes the image when the image definition is changed.
Use an adapted version of the provided evaluation script to run various checks.
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.
Adds a workflow that is based on the provided evaluation script to test functionality. Checks that depend on features that are not part of the upstream are not active.
I will not able to test the setup on GitHub until next month as I ran out of minutes for this month but it works locally when tested with act (with the appropriate modifications to use the locally built Docker image).
Before the merge, the image tags in the
checkworkflow need to be updated according to the branch the PR is merged and the tag the image is given as a consequence. Also, ideally the evaluation script (or a version of it) would be pushed into the repository by its actual owner (or at least with them noted as the developer) to provide correct attribution.