# Smoke-testing plugins during upgrade process

**URL:** <https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118>\
**Category:** Feature\
**Created:** [October 1, 2017, 8:18am UTC](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118 "2017-10-01T08:18:48Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [October 2, 2017, 9:04am UTC](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118/18 "2017-10-02T09:04:27Z")

</div>

For starters, the only way of enabling a plugin now is by doing a full rebuild, so that is a killer here. We would need to build a system that allows you to enable/disable plugins from `/admin` which requires a whole bunch of work.

I think the first task here regardless is “enable / disable” buttons in `/admin/upgrade` that knows to talk to the server and restart it. (note, none of this work is really reusable for our internal hosting something that makes me not super enthused about doing it now)

---

_[View the full topic](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118)._