Austin

I am not sold on this idea. _In general_ I do not want to special-case any pipeline steps unless 1. It's very difficult or complex for end-users to mock up...

Why wouldn't folks just choose the right behavior and mock up `retry()` themselves? e.g. ```groovy def "all attempts fail"() { setup: getPipelineMock("retry")(_ as int, _ as Closure) >> { _args...

In summary: 1. There is not one single correct behavior for `retry(N) { ... }` in every case, so hardcoding a single special case in jenkins-spock will always be wrong...

Could you share line numbers of the locations where the File object's taking in a path with url encoding?

@kamilszymanski , thank you! I have not had a chance to look yet, but it's on my radar and I'll let you know when I have.

I took a look! Oh boy, what fun! https://github.com/homeaway/jenkins-spock/tree/issue-22/examples/shared-library-gradle # Transitive Dependency JARs from Jenkins Plugins There is a problem that hopefully someone with Gradle experience can help me solve....

I haven't had time to look over the updates yet; until I find that time I won't know if there's anything I need from you.

I am _fairly_ certain that the classpath only needs to be scanned once, at "JVM-that's-going-to-run-tests" initialization-time; not per test suite class. This would cause `jenkins-spock` to ship with ... _most_...

At the moment, I cannot think of such a way. We'd probably have to modify the implementation of `getPipelineScriptForTest(...)` to automatically inject imports for all of the classes that Jenkins...

Is this the right repository for this issue? I am not sure it applies to `jenkins-spock`.