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

Workflow step for Gradle invocation

    Details

    • Similar Issues:

      Description

      gradle(...) step for workflow is desirable, so that its output gets annotated to show the list of tasks that have been executed.

        Attachments

          Issue Links

            Activity

            Hide
            douglaswpaul Douglas Paul added a comment -

            Having a gradle step that survives restarts/disconnections would be great eventually, but does that really need to hold up Gradle becoming a first-class build step? The manual tool/withEnv/sh approach is clunky, and I'm really missing the GradleConsoleAnnotator.

            Show
            douglaswpaul Douglas Paul added a comment - Having a gradle step that survives restarts/disconnections would be great eventually, but does that really need to hold up Gradle becoming a first-class build step? The manual tool / withEnv / sh approach is clunky, and I'm really missing the GradleConsoleAnnotator .
            Hide
            lorantonodi Lorant Onodi added a comment -

            I have to agree with Douglas Paul, I would really like to use gradle plugin in the my pipeline scripts instead of the sh approach. Also, as far as I am aware, the JENKINS-26055 is a "Won't Do". So what's up now?

            Show
            lorantonodi Lorant Onodi added a comment - I have to agree with Douglas Paul , I would really like to use gradle plugin in the my pipeline scripts instead of the sh approach. Also, as far as I am aware, the JENKINS-26055  is a "Won't Do". So what's up now?
            Hide
            wolfs Stefan Wolf added a comment -

            Lorant Onodi: What would you expect to be supported as part of the pipeline DSL? What are your use cases?

            I would look into implementing better support for pipeline but first I would like to know what should be supported and what the DSL would look like.

            Show
            wolfs Stefan Wolf added a comment - Lorant Onodi : What would you expect to be supported as part of the pipeline DSL? What are your use cases? I would look into implementing better support for pipeline but first I would like to know what should be supported and what the DSL would look like.
            Hide
            alexbrjo Alex Johnson added a comment - - edited

            This is being considered as part of the Important Pipeline Compatibility Epic. Here are the tasks to get this plugin to a basic level (not a durable task) of pipeline compatibility:

            • Refactor to use Pipeline compatible APIs
            • Add withGradle() builder step as an improved workaround for a bash shell step
              • Would provide GradleConsoleAnnotator and would use environment vars
            • Test that pipeline can run and Gradle console output can be annotated
            • Manual test to confirm step runs in pipeline with console annotator
            Show
            alexbrjo Alex Johnson added a comment - - edited This is being considered as part of the  Important Pipeline Compatibility Epic . Here are the tasks to get this plugin to a basic level (not a durable task) of pipeline compatibility: Refactor to use Pipeline compatible APIs Add withGradle() builder step as an improved workaround for a bash shell step Would provide GradleConsoleAnnotator and would use environment vars Test that pipeline can run and Gradle console output can be annotated Manual test to confirm step runs in pipeline with console annotator
            Hide
            recampbell Ryan Campbell added a comment -

            We are splitting the withGradle and ConsoleAnnotator into JENKINS-44834 and leaving this issue targetted at the original request for a gradle step. We believe that JENKINS-44834 will address the core use-cases which gradle users expect from gradle integration with pipeline.

            Show
            recampbell Ryan Campbell added a comment - We are splitting the withGradle and ConsoleAnnotator into  JENKINS-44834 and leaving this issue targetted at the original request for a gradle step. We believe that  JENKINS-44834 will address the core use-cases which gradle users expect from gradle integration with pipeline.

              People

              • Assignee:
                gbois Gregory Boissinot
                Reporter:
                kohsuke Kohsuke Kawaguchi
              • Votes:
                45 Vote for this issue
                Watchers:
                54 Start watching this issue

                Dates

                • Created:
                  Updated: