-
Notifications
You must be signed in to change notification settings - Fork 673
Home
Brent Cook edited this page Jun 11, 2020
·
7 revisions
- Merge a PR to master on metasploit-payloads first. Every merge to master will build a new Gem automatically!
- After about 20 minutes, the gem will be built and show up here: https://rubygems.org/gems/metasploit-payloads
- On your metasploit-framework PR, update metasploit-framework.gemspec to point to the new gem version
- In metasploit-framework, run
bundle update
to update the Gemfile* files - In metasploit-framework, run
./tools/modules/update_payload_cached_sizes.rb
to update the payload cached sizes - Commit Gemfile.lock, metasploit-framework.gemspec, and cache size changes, then test, merge, and enjoy!
If you do land a PR, do a gem build and things are busted, don't fear! Just make a fix, land it to master, and build another gem. Gems are cheap, just build another one. It is technically possible to delete a bad gem, but it is almost never worth the effort. We never want to release a gem twice with the same version number.