Don't pin Java version in the pipeline, let maven decide
Do not pin the Java version used to run maven

The EGit and EGit-Github maven builds have been made to be able to
use any Java >= 1.8 for running the maven build. They will execute
the tests on a Java version determined by the BREE specified in the
MANIFEST.MF files (currently JavaSE-1.8).

The mechanism relies on the CI infrastructure providing a maven
toolchain definition for at least that BREE.

Change-Id: Ie83f986e54ae11cef5ce363d404ddf137eccf714
Signed-off-by: Thomas Wolf <>
4 files changed
tree: e72265c1bf019088637195121974c6768bd41d90
  1. .classpath
  2. .gitignore
  3. .project
  4. .settings/
  7. src/
  8. vars/

EGit Jenkins Pipelines

This repository contains the EGit Jenkins pipeline library.

For general information about Jenkins pipeline shared libraries see the Jenkins documentation.

Jenkins pipelines are written in Groovy; for development in Eclipse it may help to install the Groovy Development Tools. Be aware, though, that GDT patches the JDT Java compiler; a particular version of GDT thus works only with a particular version of JDT. If you use an Eclipse I-build (nightly development build for the next release), GDT will fail to install.

The library is intended to be used for the Jenkins builds of the egit/egit and the egit/egit-github repositories.

It provides several kinds of general pipelines that can be configured:

  • verifyBuild is a simple pipeline that builds and runs the tests for a Gerrit patch set.
  • productBuild is intended to be run when a Gerrit patch set is submitted and builds a full distribution (nightly or stable build).

uiNode encapsulates the general Jenkins slave setup to run a build including UI tests on a JIRO node.

Directory src contains auxiliary Groovy classes encapsulating generally useful operations.


The content of this repository is licensed under the EPL 2.0.

SPDX-License-Identifier: EPL-2.0