# Kibana plugin standalone build

**URL:** <https://discuss.elastic.co/t/kibana-plugin-standalone-build/263282>\
**Category:** Kibana\
**Created:** [February 4, 2021, 6:30pm UTC](https://discuss.elastic.co/t/kibana-plugin-standalone-build/263282 "2021-02-04T18:30:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zixon89](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zixon89/32/81386_2.png) [@zixon89](https://discuss.elastic.co/u/zixon89)\
**Post date:** [February 4, 2021, 6:30pm UTC](https://discuss.elastic.co/t/kibana-plugin-standalone-build/263282/1 "2021-02-04T18:30:21Z")

</div>

Hi there,

I'm still fresh with Kibana plugin development, so currently I'm doing building by using this ([Getting started | Kibana Guide [7.10] | Elastic](https://www.elastic.co/guide/en/kibana/current/development-getting-started.html)) guide:

- Clone Kibana repo
- Set my plugin inside kibana's plugin folder
- Run yarn kbn bootstrap
- Run yarn build

Is there a way to do a bootstrap and run build without fetching whole kibana repo?

Thanks,  
Nikola

---

<div class="post-metadata">

**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\
**Post date:** [February 4, 2021, 7:07pm UTC](https://discuss.elastic.co/t/kibana-plugin-standalone-build/263282/2 "2021-02-04T19:07:25Z")

</div>

You can't do a bootstrap/build without fetching the repo, but you could download a built version of both ES and Kibana, then put your plugin inside the `plugins/` folder of the Kibana folder. However, you'll have to restart Kibana every time you make a change to your plugin, unlike if you are running from src, which will automatically take care of this bundling for you. Hope that helps.

---

<div class="post-metadata">

**Author:** ![zixon89](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zixon89/32/81386_2.png) [@zixon89](https://discuss.elastic.co/u/zixon89)\
**Post date:** [February 4, 2021, 8:56pm UTC](https://discuss.elastic.co/t/kibana-plugin-standalone-build/263282/3 "2021-02-04T20:56:52Z")

</div>

Hi @lukas,

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?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 4, 2021, 8:57pm UTC](https://discuss.elastic.co/t/kibana-plugin-standalone-build/263282/4 "2021-03-04T20:57:40Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.