It's a trap - Jenkins as a self-service user interface

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.

  • When Jenkins stops scaling
  • Lack of context and state
  • A flat user interface
  • Coupled UI, backend and API

Fill in your details and we'll send the ebook your way