[WIP] [JENKINS-46790] Expose a RecipientProvider for ownership #76
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.
See JENKINS-46790
NOTE: This is just a quite basic implementation, copy/paste based with some minor tweaks, without any UTs. Just implemented with the purpose to expose the current implementation and get some early feedback whether it's a good approach and even without any manual yet!
Highlights:
token-macro
to be able to use email-extstruct
dependency to support theSymbol
annotation.Questions:
email-ext
UTs usesPowerMock
while this plugin uses theJenkinsRule
framework, what's the best approach to add some test coverage?co-owners
recipient list. What do you think?