-
Improvement
-
Resolution: Fixed
-
Minor
-
None
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
- 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
[JENKINS-47718] Deprecate User.getUser(String)
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Link |
New:
This issue is related to |
Summary | Original: Deprecate User.getUser() | New: Deprecate User.getUser(String) |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |
The API misusage also causes
JENKINS-23281in some cases