Symlink foreman-test script to /usr/local/bin#683
Merged
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
jeremylenz
approved these changes
Jul 20, 2026
jeremylenz
left a comment
Contributor
There was a problem hiding this comment.
Works as expected!
ACK 👍
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
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.
Why are you introducing these changes? (Problem description, related links)
Foreman merged a generic plugin test runner script (
script/foreman-test) in theforeman/foreman#10963. This script replaces ad-hoc per-plugin test wrappers likektestwith a unified tool that works across all plugins. In the development VM, the script lives inside the Foreman checkout and isn't on PATH, so developers have to invoke it with a full path.What are the changes introduced in this pull request?
/usr/local/bin/foreman-testto thescript/foreman-testinside the Foreman checkout, placed right after the git repository clone step in theforeman_developmentrole.How to test this pull request
Steps to reproduce:
./foremanctl deploy --foreman-initial-admin-password=changeme --tuning developmentls -la /usr/local/bin/foreman-testforeman-test --helpfrom any directory and confirm it prints usage informationChecklist