I noticed that
public/plugins/ requires to be on a read/write mount, which is awkward as this is code under git control…
I wanted to fix that … but I got to the part where you install plugins … and I find that part a bit awkward… could you please (if you remember ) tell me the rationale behind the plugin activation part here:
I see you first create the target dir … then brutally clean it up … then symlink it…
In the commit messages, I see something about not breaking Jenkins … (so possibly the rationale is stale…).
I’d be happy to try and have a stab at this… (and generally going over the whole thing making sure nothing under git control is on R/W mounts).