Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: core
-
Labels:None
-
Similar Issues:
Description
User#getUser() method causes lots of confusion for plugin developers. It implicitly creates a user if it cannot be found, and in many cases this is actually a not-expected behavior
I propose to deprecate the method and to create a new User#getOrCreate() which would be more explicit
Attachments
Issue Links
- is related to
-
JENKINS-23281 Jenkins.getUser(...) is debilitatingly slow with a large number of users
-
- Closed
-
-
JENKINS-43936 Performance issues caused by User.getOrCreate
-
- Resolved
-
-
JENKINS-48707 Performance: Use User#getById() instead of User#get()
-
- Resolved
-
- links to