The idea is to make automation CI-CD of just fetching plugin code and building a plugin using Jenkins, I do not want to run it, just to build and archive the plugin ZIP file on Jenkins artifacts. I want to use (as much possible) minimal storage, network and time execution on the Jenkins agent machine because of resource restrictions I have.
Since my plugin is only about 5 MB in size, it will be resource and time consuming for agent to download whole kibana repo for simple build that takes around 20 sec to build, because agents are configured in a way to clear their workspace upon job finish.
That's why I thought that there is some standalone Kibana tool(s) that I could download just to build plugin.
If downloading the built version of Kibana is only option, it's better fetching around 200-300MB instead of couple of GB of source code.
Do I really need built ES just for building a ZIP version of plugin?