JenkinsIcon indicating the project type

Jenkins

Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26635

Provide Groovy workflow build step

    Details

    • Type: New Feature
    • Status: In Review (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: groovy-plugin
    • Labels:
    • Environment:
      Jenkins 1.580.2.1
      Workflow (all) 1.1
    • Similar Issues:
    • Epic Link:

      Description

      Provide a built in step in its own interpreter for running Groovy code to separate it out from the workflow DSL.

      Although its possible ti run a groovy script from within the sh task having a native capability would be better.

      NB this is blocked by https://issues.jenkins-ci.org/browse/JENKINS-26055

        Attachments

          Issue Links

          depends on

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-26055 DurableTaskStep

          • Major - Major loss of function.
          • Reopened

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-37011 Provide a way to write full-fledged Steps in CPS-transformed Groovy

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is related to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-26192 Add support for Grape (@Grab) in workflow scripts

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link PR 22

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            tg9541 Thomas Goeppel added a comment - - edited

            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

            Show
            tg9541 Thomas Goeppel added a comment - - edited 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
            Hide
            Permalink
            jglick Jesse Glick added a comment -

            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.

            Show
            jglick Jesse Glick added a comment - 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.
            Hide
            Permalink
            tg9541 Thomas Goeppel added a comment -

            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 ).

            Show
            tg9541 Thomas Goeppel added a comment - 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 ).
            Hide
            Permalink
            docwhat Christian Höltje added a comment -

            This would still be nice to have for system groovy scripts, assuming the script approval stuff would still work.

            It would be handy for maintenance jobs.

            Show
            docwhat Christian Höltje added a comment - This would still be nice to have for system groovy scripts, assuming the script approval stuff would still work. It would be handy for maintenance jobs.
            Hide
            Permalink
            jglick Jesse Glick added a comment -

            JENKINS-37011 should make this much easier to implement; needs to be prototyped.

            Show
            jglick Jesse Glick added a comment - JENKINS-37011 should make this much easier to implement; needs to be prototyped.
            Hide
            Permalink
            jglick Jesse Glick added a comment -

            nice to have for system groovy scripts

            All Pipeline script is essentially “system Groovy” already: you can access Jenkins internal types, subject to script security.

            Show
            jglick Jesse Glick added a comment - nice to have for system groovy scripts All Pipeline script is essentially “system Groovy” already: you can access Jenkins internal types, subject to script security.
            Hide
            Permalink
            jglick Jesse Glick added a comment -

            PR 22 now offers a withGroovy step.

            Show
            jglick Jesse Glick added a comment - PR 22 now offers a withGroovy step.
            Hide
            Permalink
            docwhat Christian Höltje added a comment -

            Link to PR22 which still needs a review.

            Show
            docwhat Christian Höltje added a comment - Link to PR22 which still needs a review.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                nharniman Nigel Harniman
              • Votes:
                9 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated: