We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
runRemotely
I have discovered a usability flaw in #882, that
rr.runRemotely(r -> someStatement());
(where someStatement is a method returning void) does not compile, as javac tries to use Step2 when Step was meant. You can work around it via
someStatement
void
Step2
Step
rr.runRemotely((RealJenkinsRule.Step) r -> someStatement());
or
rr.runRemotely(r -> {someStatement();});
but both are awkward. It would be better to introduce aliases like run(Step) + call(Step2) which would more identify the expected lambda type.
run(Step)
call(Step2)
The text was updated successfully, but these errors were encountered:
java.util.function.Function
No branches or pull requests
I have discovered a usability flaw in #882, that
(where
someStatement
is a method returningvoid
) does not compile, as javac tries to useStep2
whenStep
was meant. You can work around it viaor
but both are awkward. It would be better to introduce aliases like
run(Step)
+call(Step2)
which would more identify the expected lambda type.The text was updated successfully, but these errors were encountered: