-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Secret hiding base CI resource #5096
base: feature/secret-hiding
Are you sure you want to change the base?
Secret hiding base CI resource #5096
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## feature/secret-hiding #5096 +/- ##
======================================================
Coverage 83.14% 83.14%
======================================================
Files 248 248
Lines 26923 26923
======================================================
Hits 22386 22386
Misses 4537 4537
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
37b9dcc
to
3bca636
Compare
dae2d55
to
451a7d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also add the "kernel builds" integration test as part of this? Just so that the code is tested/used straight away
|
||
# Finally run olddefconfig again to make sure any | ||
# new options are configured before build | ||
make olddefconfig |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add some sort of assertion here to verify that .config contains everything we specify in kernel_config_overwrites? Just as a sanity check, to avoid ever running into any hard/weird to debug issues
070590a
to
ffcab3f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice!!
.buildkite/pipeline_pr.py
Outdated
pipeline.build_group_per_arch( | ||
"🕵️ Build Secret Hiding Kernel", | ||
pipeline.devtool_test( | ||
pytest_opts="-m nonci integration_tests/build/test_hiding_kernel.py", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mh, I guess as long as we don't setup an nightly pipelines, reusing nonci
is fine, but if we ever have a nightly pipeline on this branch that also passes -m nonci
, then it might pick up this test by accident, which we don't want probably. Thought on using a dedicated pytest mark for this test? :o
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a new secret_hiding mark for the test
ffcab3f
to
c02988a
Compare
c02988a
to
cc851c5
Compare
Creating a script to build and install a modified kernel with patches applied. Signed-off-by: Jack Thomson <jackabt@amazon.com>
Update the script to allow it to run the build without installing. Allow us to add patches in different formats, we now allow .lore files which are a link to the patch series, these will be automatically downloaded and applied. We also accept .mbox files which again will be patched onto our kernel. Signed-off-by: Jack Thomson <jackabt@amazon.com>
Adding a new integration test to assert that the kernel build script will succeed. Signed-off-by: Jack Thomson <jackabt@amazon.com>
cc851c5
to
9a7c7e9
Compare
Changes
Adding the base script to be used for building custom kernels with secret hiding patches applied for testing
Reason
...
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md
.PR Checklist
tools/devtool checkstyle
to verify that the PR passes theautomated style checks.
how they are solving the problem in a clear and encompassing way.
in the PR.
CHANGELOG.md
.Runbook for Firecracker API changes.
integration tests.
TODO
.rust-vmm
.