Thanks for your advice about this - you clearly have been digging this a lot more than I have with my quick-shot random request!
Your presumption that I want to disable the whole UI sequence is correct - this would be a scripted install initiated by a Configuration Management system. At a high level, the install sequence is:
- Install prerequisite software packages (Java JRE/JDK, etc)
- Install Jenkins
- Set startup properties
- Start Jenkins
- Install Jenkins plugins (via jenkins-cli or REST API)
- Configure Jenkins settings (probably REST API)
- Configure jobs (via jenkins-cli or REST API)
In this particular pipeline, there's not many jobs, they're not very complicated and it's not mission-critical. Consequentially, the view is that this environment is mostly disposable. When/if any issues arise, the environment will be destroyed and re-created using the CM system.
Since raising this issue, I have realised that I can manually assemble the various components through the CM system, bypassing the installer completely. While probably not ideal, it addresses my immediate need, therefore I have downgraded the priority on this issue to Trivial.
Perhaps this issue can be fed into the next major update?