Gradle

Run Gradle builds inside Jenkins with version pinning, report ingestion, and parameter mapping — integrated natively with Opsera's pipeline builder.

Prerequisites

• Jenkins tool registered in Opsera Tool Registry

• Jenkins Job created with job type set toGradle

• SCM repository with Gradle project registered

Pipeline setup

1

Create build step

Tool = Jenkins, Step Type = Build. In Step Settings choose the Jenkins Tool and the Gradle job

2

Configure source and commands

Select SCM tool, Repository, and Branch. Enter single or multiple build commands. Define Input and Output Parameters as needed.

3

Add report ingestion (optional)

Enable the Report Details toggle to ingest test report files directly — eliminates the need to specify report paths in command-line scripts.

4

Select Gradle version

Use the Dependency dropdown to pin a Gradle version: 6.9.4, 7.5.1, 7.6.4, or 8.6.

Points to remember

• Always pin a specific Gradle version via the Dependency dropdown — using an unpinned version can cause unexpected build behavior when Gradle releases updates.

• Input parameters provide initial data to start build execution; output parameters represent artifacts and results produced by the pipeline stages.

• The Report Details toggle eliminates the need to hardcode report file paths in your command-line scripts, making pipelines more portable.

FAQs

Which gradle versions are supported?

Opsera supports Gradle 6.9.4, 7.5.1, 7.6.4, and 8.6. Select the version from the Dependency dropdown in Step Settings.

Can I run multiple Gradle commands in one step?

Yes. Enter each command on a new line in the Commands field — Opsera executes them sequentially in order.