-
New Feature
-
Resolution: Unresolved
-
Minor
Please add general support for Grape in every groovy script.
This could be done by adding ivy to the Jenkins classpath
Since Jekins supports groovy scripting in many places, it would be best to handle it globally, not inside specific plugins.
Background:
if you use @Grab and @Grape annotations inside any kind of groovy scripts, you will get this error:
java.lang.NoClassDefFoundError: org/apache/ivy/core/report/ResolveReport
Reason: grape personal dependency ivy is not present on Jenkins classpath
see: https://groups.google.com/forum/#!topic/jenkinsci-issues/wMdNET2L3TU
There is a solution only for 'job-dsl-plugin', but a general support would be more suitable:
see also: https://issues.jenkins-ci.org/browse/JENKINS-16361
and https://issues.jenkins-ci.org/browse/JENKINS-18349
and https://issues.jenkins-ci.org/browse/JENKINS-18400
- is related to
-
JENKINS-18400 Add Grape @Grab Support to Scriptler Plugin
- Open
-
JENKINS-18484 Add Grape @Grab support to flow-dsl plugin
- Open
-
JENKINS-18349 Allow to use @Grab in a Script Console
- Open
-
JENKINS-27012 Add @Grab grape support to facilitate dependency injection
- In Progress
-
JENKINS-26192 Add support for Grape (@Grab) in workflow scripts
- Resolved
-
JENKINS-16361 @Grab Grape support
- Closed