[JIRA] [groovy-plugin] (JENKINS-26635) Provide Groovy workflow build step
Title: Message Title Thomas Goeppel commented on JENKINS-26635 Re: Provide Groovy workflow build step In March I didn't know about '@NonCPS import', and in the meantime I've found work-arrounds using standard Groovy libraries and @NonCPS Groovy functions, and serializable CPS built-in types. On executor nodes I now run Groovy wrapped in Gradle tasks. I've removed my vote for the ER, but a Workflow compatible Gradle build step would still be nice ( -> JENKINS-27393 ). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26635) Provide Groovy workflow build step
Title: Message Title Jesse Glick commented on JENKINS-26635 Re: Provide Groovy workflow build step Needs to allow selection of JRE and Groovy installation, but with a fallback to the JRE of the slave agent and the Groovy library used by Workflow itself, so that there is no special prerequisite on the slave for typical cases. Along with other command-line options, classpath customization needs to be allowed though in most cases (public libraries) you can just use @Grab. Could even allow passing Serializable objects as input and output with the help of a wrapper script, though I see no straightforward way to share instances of classes defined in the script itself. Still might be useful even if limited to built-in types like Map and Collection plus String and primitives. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26635) Provide Groovy workflow build step
Thomas Goeppel commented on JENKINS-26635 Provide Groovy workflow build step Getting data in, and out of such a Groovy build step should be as easy, and unobstrisive as possible: data in - e.g. env, data out - e.g. map like in Workflow Input step adding jars to the class path should be simple - e.g. cp relative to workspace in Groovy tool configuration 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-26635) Provide Groovy workflow build step
Thomas Goeppel edited a comment on JENKINS-26635 Provide Groovy workflow build step Getting data in, and out of such a Groovy build step should be as easy, and unobstrisive as possible: data in - e.g. env, data out - e.g. map like in Workflow Input step adding jars to the class path should be simple - e.g. cp relative to workspace in Groovy tool configuration "data out" is maybe the same as JENKINS-26133 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-26635) Provide Groovy workflow build step
Nigel Harniman updated JENKINS-26635 Provide Groovy workflow build step Change By: Nigel Harniman (27/Jan/15 3:56 PM) Summary: ProvideGroovyworkflow build step Description: Provideabuiltinstepinitsown intepreter interpreter forrunningGroovycodetoseparateitoutfromtheworkflowDSL.Althoughitspossibletirunagroovyscriptfromwithintheshtaskhavinganativecapabilitywouldbebetter.NBthisisblockedbyhttps://issues.jenkins-ci.org/browse/JENKINS-26055 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.
