Curated vulnerability data for the Freedesktop systemd
Please see your course website for instructions. This README is more for people managing this data.
- You'll need Ruby 2.4+
- Run
gem install bundler
(if you don't already have bundler) cd
to the root of this repo, runbundle install
- Run
bundle exec rake
If the output has no failures, then it checks out!
To clone the repo into this folder, use this command:
git clone https://github.com/systemd/systemd.git tmp/src
We do this manually... at the moment.
Here's how you merge in student data once the assignment is finished.
- Make sure the current
dev
branch is updated and works with the build - Switch
vulnerability-history
locally to pull fromdev
instead ofmaster
. - Squash and merge the student pull req into
dev
- Run
rails data:systemd
locally. When it says "Loading data version " and then a git hash, make sure that matches up with the latest merge you just made (so you know you are pulling the latest chromium-vulnerabilities data). Alternatively, you can dorails data:clear data:systemd:load_only
which goes quicker. - If all is well, then do any spot-checks of their data to make sure everything got tagged just fine.
- If all is not well:
- You may need to merge their changes with any of your changes. This might be on GitHub itself, or locally.
- You may need to correct their YML structure to make it compatible with the loader. Make the change locally and push back to
dev
to fix it and re-run. - If things fail on an exception, you can always put in this snippet somewhere to figure out what file failed and use byebug to figure out the problem:
begin
# code where things when wrong
rescue
byebug
end
- You can always do
rails data:systemd:nogit
to reload things without hitting GitHub - helpful for quicker debugging.
After we merge in a bunch of PRs, here's a checklist of what needs updating, and in what order:
- Add mentioned commits (default options should be good enough)
- Generate weeklies (skip existing)