-
Notifications
You must be signed in to change notification settings - Fork 564
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
ghidra: update CI Workflow to reflect recent Ghidrathon changes #1976
Comments
Thank you for opening, great idea! With the latest changes to Ghidrathon we can download the pre-built extension and remove the Gradle build steps from our CI workflow. |
Hello, can I please take this up? I also noticed version upgrade is needed for jep and ghidrathon, should I bump up version in this change? |
Thank you for reaching out @psahithireddy - I've assigned this issue to you. The goal here is to update capa's existing Ghidra test workflow to leverage the simplified Ghidrathon v4 installation steps outlined in its README. Specifically, we want to substitute building Ghidrathon with downloading the latest pre-built release from GitHub. As you already mentioned, let's also update the versions:
Reach out here if you have any questions! 🚀 |
Hi @mike-hunhoff, I have few questions
|
The Ghidrathon-v4.0.0.zip file contains three files:
So the first step here is to update the CI workflow to download and extract the Ghidrathon-v4.0.0.zip file instead of building it from source. |
Understood. My apologies for the bad PRs, I now found a way to trigger ci workflow to test it without PR, in my local. Should I update the CHANGELOG too? Thanks a lot for your help! |
closed by #2020 |
Summary
The latest release candidate for Ghidrathon now includes an installation script. This now outdates the method used in the Ghidra backend's CI workflow. Please update the workflow to use the new installer.
The text was updated successfully, but these errors were encountered: