Hello, I have a setup of around 25 Jenkins jobs running on various jenkins slaves. My requirement is that anybody who is logged in into Jenkins, should be able to "Build" the job. However, there are couple of jobs amongst them which should only be "Build"able by specified users. I have already looked at "Project Based Matrix Authorization Strategy" and "Role-Based Strategy". In both of these configurations, Application level permissions overrule project/job level permissions.
Thus, if user has global "Build" permissions, there is no way he can be restricted from executing the project unless I remove global "Build" authorization and manage it at project level. That means, I will have to reconfigure existing jobs so that logged in user can continue to "Build" projects as they have been. Instead, is there any project level configuration under which Jenkins can prompt for some security key when users try to "Build" particular project. Thus whoever has that password will only be able to build particular project but other projects still remain "Build"able for all without any changes and minimal configuration. Thanks, Kamlesh -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/807f0475-9926-40a5-a23d-75e659de3980%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
