It’s a Trap - Jenkins as Self-Service UI
Enabling Jenkins self-service can work well for developer self-service, but there are many known visibility, compliance and other issues that stem from the inherent openness of Jenkins. At some point the speed and flexibility can turn into a mess. There’s a better way to do self-service (and not with Jenkins self-service), solving for a great developer experience and creating much less devops bottlenecks and surprises. It’s called a developer portal, or a software/resource catalog.