We have had some success using the CloudBees Folders Plugin. I think
it does a pretty good job of at least keeping job configurations
separate on the Jenkins master. It allows credentials to be tied to a
particular folder too.
As far as isolating our tenants' build artifacts from each other, I
have found that to be a little trickier. We've planned for it but
haven't implemented it. We are thinking using SSH Slaves with
different Unix users may be good enough, or even wholly separate VMs
for tenants -- depending on what the needs are really. In either case,
you can then use the Job Restrictions plugin to restrict on which
slaves the job can run.
Maybe that gives you enough to go on. We haven't grown to need the
kind of isolation we planned for, so our setup has not really been
tested. Maybe someone else on the list has more experience in that
regard.
> --
> 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
jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/jenkinsci-users/ce35b4e2-3eda-48c9-a16e-236dcf43f911%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.