-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminology Cleanup: Introduce createAgent()
and createOnlineAgent()
in JenkinsRule
#337
Terminology Cleanup: Introduce createAgent()
and createOnlineAgent()
in JenkinsRule
#337
Conversation
…()` in `JenkinsRule`
Co-authored-by: offa <[email protected]>
Co-authored-by: offa <[email protected]>
Thanks for the review @offa ! |
@oleg-nenashev I've created a PR for your branch which fixes the conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-0 I guess. Just adds complexity to the API surface. Would prefer to limit renames to user-facing strings.
@@ -903,39 +903,89 @@ public File createTmpDir() throws IOException { | |||
return env.temporaryDirectoryAllocator.allocate(); | |||
} | |||
|
|||
// TODO replace return types once the Jenkins core is updated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you really foresee such a class rename in core? Seems like a lot of disruption for a cosmetic issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not expect it anytime soon TBH. Depends on contributions though
More inclined to just use the new terminology incrementally as changes are made, as in #428. |
Cleans up API for JenkinsRule. I did not touch
HudsonTestCase
, because we might want to drop JUnit 3 support alltogether