CI: Refactor for multi target ghidra - #83
Open
dreamsyntax wants to merge 1 commit into
Open
Conversation
dreamsyntax
force-pushed
the
master
branch
2 times, most recently
from
June 4, 2026 17:17
b1048ff to
9836d96
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've updated the CI flow to use the setup-ghidra action, similar to how we did it in ghidra_psx_ldr.
I've taken care to match how you were running tests on all 3 target platforms, specifically because of the XbSymbolDatabase binaries.
I've marked the two areas to set the Ghidra versions with
# GHIDRA VERSIONSI opted to do every version of Ghidra 12.
I only run the tests against latest (12.0.4) because of rate limits with the amount of setup requests running against all does.
It can still happen with the number of runners unfortunately - as you can see here https://github.com/dreamsyntax/ghidra-xbe/actions/runs/24856148177/job/72769728906.
Passing GITHUB_TOKEN to attempt to avoid that.
I verified each test does pass on 12.0 - 12.0.4 before opening this.
This makes the
build.shscript redundant, but I left it in the repo incase people use it for local setups.Also updated the current github actions versions.
The flow is:
build-YYYYMMDDHHMMformat the old script did, whenever master is updatedExample successful workflow in master:
https://github.com/dreamsyntax/ghidra-xbe/actions/runs/24856148177
Example release artifacts (auto generated from above)
https://github.com/dreamsyntax/ghidra-xbe/releases
Lastly thank you for all the effort on this! I've been using this extension quite regularly lately and its been a great help!