craig Brookes It already uses the "jenkins-persistent" plugin by default - but with no customization (can't define memory, disk space, etc).

1. Should we first require an already existing jenkins instance and then select one when provisioning it?
2. If we are provisioning jenkins (be it optional or not), should we would use the same "view" that is used in the jenkins deployment under ci/cd?