Hi I am working on a small Jenkins server to be shared between a handful of users. Ideally there would be complete isolation between projects, but as I've come to understand the execution environment that's not really an out-of-the-box thing. In weighing the amount of work that would go into complete isolation against ease of setup, I think it would be good enough if I can at least separate execution environment from the Jenkins configuration (e.g. so at least system configuration is not readable). I think the swam plugin is a good way to do this since the build runs as a separate Unix user.
I'm using LDAP for authentication and project-based matrix authorization. I have it set up that if a user is in a certain LDAP group they have superuser privileges across the whole site. The idea is the sysadmin will grant a Jenkins project to whomever needs it and we will hope they will play nice with each other. So my swarm clients apparently need a user and password to connect, and the only way I've managed to get this to work is by using an LDAP usersname and password. I am looking to to swarm client authentication either by host (I will just need localhost) or some way I can use a local Jenkins user in conjunction with LDAP. Any help or alternative ideas are appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
