How do I scope locks so that on team's lock names don't accidentally collide with another's?
They seem to be created at server level rather than at folder level. Any advice or patterns? Right now I'm telling folk to be careful with naming. More generally... from a resource management point of view it would seem that Jenkins would benefit from all "names" being scopeable to something narrower than global as this would reduce the admin burden and improve self service without increasing risk. Folder names are inherently scoped, and credentials can be created at folder scope, but what about node names and labels, or lock names or other such objects? And then we can also talk about permissions. Who should be permitted to obtain a given lock and who not? -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bfef09f0-31fd-4ac6-bb7b-5beeb484e303%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
