[JIRA] [groovy-plugin] (JENKINS-18349) Allow to use @Grab in a Script Console
Kenneth Baltrinic commented on JENKINS-18349 Allow to use @Grab in a Script Console I have added a separate ticket for the workflow plugin: JENKINS-26192 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-18349) Allow to use @Grab in a Script Console
Kenneth Baltrinic edited a comment on JENKINS-18349 Allow to use @Grab in a Script Console Perhaps I don't understand the terms clearly either so I will attempt to be a descriptive as possible. First this is with Jenkins v 1.592 which has the Hudson Groovy Builder 1.24 installed and all of the Workflow 1.0 plugins installed. In its earlier version Hudson Groovy Builder appears to have also been called the "Groovy Plugin." With this combination of components, @Grab works when using the "Execute Groovy script" option within a free-style job (this is what I meant above the "Groovy Plugin" and "Groovy build step".) To my knowledge this is the only place that it works. The locations I specifically have tried and confirmed not to work are: In the Groovy Console: Jenkins > Manage Jenkins > Script Console In workflow jobs, in the Workflow Definition when using Groovy CPS DSL. A coworker of mine on a slightly older build (1.552) also reports that he gets the same error when attempting to use @Grab with the Build Flow Plugin (v 0.10). I have not contacted the reporter but am presuming this to be the same issue because I am getting the same error in what I presumed to be the same location (i.e. I interpret his reference to the "Groovy Script console" to be the same location as I referenced in #1 above.) I am not clear on what his original reference to "System Groovy Scripts" refers to but it seems to yet a forth location where @grab does not work. As to whether or not this is a single issue with a common root cause and solution or multiple issues that will each need their own resolution, I will defer to more knowledgable heads. However there already are several other tickets open about adding @Grab support to various plugins, etc: JENKINS-15512, JENKINS-16361, JENKINS-18400, JENKINS-18484. We just seem to be missing one for the new workflow plugin. I hope this helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-18349) Allow to use @Grab in a Script Console
Kenneth Baltrinic commented on JENKINS-18349 Allow to use @Grab in a Script Console Perhaps I don't understand the terms clearly either so I will attempt to be a descriptive as possible. First this is with Jenkins v 1.592 which has the Hudson Groovy Builder 1.24 installed and all of the Workflow 1.0 plugins installed. In its earlier version Hudson Groovy Builder appears to have also been called the "Groovy Plugin." With this combination of components, @Grab works when using the "Execute Groovy script" option within a free-style job (this is what I meant above the "Groovy Plugin" and "Groovy build step".) To my knowledge this is the only place that it works. The locations I specifically have tried and confirmed not to work are: In the Groovy Console: Jenkins > Manage Jenkins > Script Console In workflow jobs, in the Workflow Definition when using Groovy CPS DSL. A coworker of mine on a slightly older build (1.552) also reports that he gets the same error when attempting to use @Grab with the Build Flow Plugin (v 0.10). I have not contacted the reporter but am presuming this to be the same issue because I am getting the same error in what I presumed to be the same location (i.e. I interpret his reference to the "Groovy Script console" to be the same location as I referenced in #1 above.) I am not clear on what his original reference to "System Groovy Scripts" refers to but it seems to yet a forth location where @grab does not work. As to whether or not this is a single issue with a common root cause and solution or multiple issues that will each need their own resolution, I will defer to more knowledgable heads. I hope this helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-18349) Allow to use @Grab in a Script Console
Daniel Beck commented on JENKINS-18349 Allow to use @Grab in a Script Console Kenneth Baltrinic: To clarify, the 'Groovy script' build step is not affected (unsurprising, as it's a straightforward groovy invocation), but the 'system Groovy script' build step in Groovy plugin is? Regarding scope, did you contact the reporter or is that your interpretation of this report? (Note that not too long ago, component names did not have the '-plugin' suffix making it difficult to tell in some cases whether a report is about the "something" related features in Jenkins, or the "something plugin".) I'm asking because I'd like to split this into one issue per component. This way (IMO) the issues have a change to actually get implemented by the respective plugins'/core maintainers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-18349) Allow to use @Grab in a Script Console
Kenneth Baltrinic commented on JENKINS-18349 Allow to use @Grab in a Script Console This is about the Script Console and pretty much every place but the Groovy Plug-in and Groovy build step. Perhaps most importantly moving forward, this issue impacts scripts run by the Workflow plug-in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
