[JENKINS-25083] use MailAddressResolver for retrieving user email instead of UserProperty #154
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tead of UserProperty
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses [build-user-vars-plugin] - Improper resolution of user e-mails](https://issues.jenkins.io/browse/JENKINS-25083)
Follow-up to: Commit 3ff2b523e9663b485ed0cbdb3ab129b64bd5e179
The previous implementation for resolving user email addresses directly utilized UserProperty, which was identified as an improper method for this task. Instead, MailAddressResolver should be used which is specifically designed for inferring email addresses.
Submitter checklist