We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
run
Is your feature request related to a problem? Please describe.
When working on a "core" plugins there does not seem to be OOTB support for the run tasks that would automatically deploy the plugin into testcluster.
Describe the solution you'd like
It would be useful to be able to do something like ./gradlew run --plugins "xx,yy" and get testcluster with core plugins xx and yy deployed.
./gradlew run --plugins "xx,yy"
Describe alternatives you've considered
I described a manual workaround here: https://gist.github.com/lukas-vlcek/26fd54fb7ba25debb5b5c5c8c390ad79
Additional context
Core plugin authors would be 😄
The text was updated successfully, but these errors were encountered:
Sounds like a good idea!
Sorry, something went wrong.
./gradlew run
#11844 has this implemented.
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
When working on a "core" plugins there does not seem to be OOTB support for the
run
tasks that would automatically deploy the plugin into testcluster.Describe the solution you'd like
It would be useful to be able to do something like
./gradlew run --plugins "xx,yy"
and get testcluster with core plugins xx and yy deployed.Describe alternatives you've considered
I described a manual workaround here:
https://gist.github.com/lukas-vlcek/26fd54fb7ba25debb5b5c5c8c390ad79
Additional context
Core plugin authors would be 😄
The text was updated successfully, but these errors were encountered: