58ba847c07
With a pure javascript plugin, dropping a new file in the plugins/ directory and reloading the page is sufficient to see changes. However, with .jar plugins (as zuul-summary-plugin now is) you need to actually issue a reload, which requires the included permissions. Enable it dev mode, which is where you'll very likely be trying to iterate development with a change to a plugin. I don't think it's really that dangerous for production, but traditionally it's been off there so let's leave it like that. While we're here, write out a little script to help you quickly deploy a new .jar of the plugin when we're testing. Change-Id: I57fa18755f8a8168da12c48f1f38d272da1c6599 |
||
|---|---|---|
| .. | ||
| docker-compose.yaml.j2 | ||
| gerrit.config.j2 | ||
| gerrit.vhost.j2 | ||
| infra_lp_creds.j2 | ||
| jgit.config.j2 | ||
| manage-projects.j2 | ||
| projects.ini.j2 | ||
| redirect.vhost.j2 | ||
| replication.config.j2 | ||
| root.my.cnf.j2 | ||
| secure.config.j2 | ||
| track-upstream.j2 | ||