-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dry run should check the remote urls #52
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh with Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue with Mark the issue as fresh with Provide feedback via https://github.com/falcosecurity/community. |
@poiana: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Motivation
We have a flag to execute driverkit in a dry run mode that actually only validates the parameters.
Since driverkit heavily depends on the correctness of the parameters passed to download the correct kernel headers/source for the current distribution it seems right to me that dry run also checks the remote URLs for the existence of the resources without downloading the final artifacts. In this way, we can run driverkit against a list of files and be confident that they will work before doing the beefy builds.
Feature
See motivation
Alternatives
Be blind
Additional context
This is needed to allow the test-infra build grid have a test step in the PRs without doing the builds every time.
The text was updated successfully, but these errors were encountered: