-
New Feature
-
Resolution: Unresolved
-
Minor
As a pipeline author who is creating pipelines for Gradle-based applications, I would like to be able to use Gradle tool definitions and console annotator in my pipeline scripts & declarative.
Acceptance criteria:
- There is a withGradle pipeline step which accepts two arguments: the tool definition name and a pipeline block wherein the given Gradle tool definition is available on the path as 'gradle'.
- Any environment variables in the tool definition will be expanded
- Any gradle executions triggered from within this pipeline block will be annotated with the Gradle ConsoleAnnotator so that user viewing the build console can easily navigate the console output.
- The ConsoleAnnotation will be automatically applied within this withGradle step and the user will have no way to disable it.
- There will be JenkinsRules which validate that a withGradle step works and that the console annotations are present in the build console of a pipeline run.
This is being considered as part of the Important Pipeline Compatibility Epic.
- is related to
-
JENKINS-27393 Workflow step for Gradle invocation
-
- Open
-
- relates to
-
JENKINS-72411 Gradle plugin pipeline console annotator doesn't work with global timestamper
-
- Open
-
Getting close to cutting a PR to start review. Noting the following acceptance criteria issues for later discussion.
Any environment variables in the tool definition will be expanded
Conflicts with variable expansion in the pipeline devguide. Variables should be treated as literals.
There is a withGradle pipeline step which accepts two arguments
No problems with the block and gradle parameters. I think other config options could be added that would be useful and quick to implement. See the Pipeline Maven Plugin for examples of extra config options. The downside of course is they would have to be tested.