-
Notifications
You must be signed in to change notification settings - Fork 129
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
Generic plugin support #491
Conversation
Neat! So we just require plugins to provide a release binary via a |
If I run the CI now, will it test anything? |
No because there is no non-python plugin that has passing tests in the repo merged atm. But i tested it on my fork (where i merged #485 and #486 and a special branch of #454 ) here: |
yes, the plugin author uses it in their tests, you don't have to do anything, see my utils.py i linked |
I was in need of getting the python bin that is using the specific test env into the setup.sh. I think there could be some other use cases for this, so i added the env variable TEST_DIR. |
1224c8d
to
4d7bef1
Compare
rebased |
4d7bef1
to
7eb9152
Compare
7eb9152
to
fb1637d
Compare
ACK fb1637d |
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
…tory with the python environment
fb1637d
to
de8f9be
Compare
@Mergifyio refresh |
✅ Pull request refreshed |
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at cb3145d |
I've thought more about #487 and since CLN supports basically any language for plugins i propose to take this generic approach instead.
Non-python plugins put their
requirements.txt
andsetup.sh
in thetests
folder (the one we already search for executing tests). The bash script will allow python developer to setup the plugin environment as they see fit.Example setup.sh from my summars plugin and then a simple switch in my utils.py for local dev and CI