HACBS JVM Build Service

This repository contains components used to deploy the HACBS JVM build service.

See each component’s directory for specific documentation.

Testing

Running Option Tests Against PRs

You can trigger the following optional tests on a pull request:

Apicurio Registry

/test jvm-build-service-in-repo-apicurio-e2e

Self Build of the JVM Build Service

/test jvm-build-service-in-repo-jbs-e2e

RHTAP Quickstarts

/test jvm-build-service-in-repo-quickstarts-e2e

WildFly

/test jvm-build-service-in-repo-wildfly-e2e

Test JVM Build Service on an OpenShift cluster

The OpenShift E2E test is programmed to run a test with following steps:

1. Create a new project in targeted OpenShift cluster and run the build pipeline which contains a Maven task from this repo to build the simple java test project

2. Make sure the pipeline succeeds and all related artifactbuilds and dependecybuilds (triggered after pipeline completion) finish successfully

3. Check that all "contaminated" builds are resolved

4. Verify that triggering a second build accesses dependencies that are cached from a previous build

5. Verify that the correct JDK version is identified in dependencybuilds

6. Check that maven/gradle logs/sources are found in rebuilt artifacts

Before running the test, you need to export couple of env vars that reference container images for the operator, cache and reqprocessor. Some existing images can be found at redhat-appstudio quay.io org (search for keyword "jvm")

Also you need to specify your quay.io username that will be used for pushing rebuilt dependencies in a format: quay.io/$QUAY_USERNAME/test-images. Make sure the repo "test-images" exists in your account and is publicly available.

export QUAY_USERNAME=<your-quay-io-account-username>
export JVM_BUILD_SERVICE_IMAGE=
export JVM_BUILD_SERVICE_CACHE_IMAGE=
export JVM_BUILD_SERVICE_REQPROCESSOR_IMAGE=
./deploy/openshift-ci.sh
make openshift-e2e