Trading-Service

The Trading Service is responsible for processing intents from players that want to buy vouchers and crediting players for ingame actions.

Development

1. Clone the Repo
2. (Required if you do not run within IntelliJ or other Java IDEs) - Install Java 21 JDK and set JAVA_HOME to the corresponding path
3. Build Project

   ./mvnw clean compile
   

Running Tests

This Service uses Maven Surefire and Maven Failsafe to run Tests.

Running Unit Tests: Either run config UnitTests or

./mvnw test

Running Integration Tests (Requires a valid Docker environment that is accessible to the current shell context) Either run config IntegrationTests or

./mvnw integration-test

Running all tests (Requires a valid Docker environment that is accessible to the current shell context): Either run config AllTests or

./mvnw verify

Running with other services

Use the local dev env as described in its readme.

1. Start everything except the Trading service itself (you still need the outbox).
2. Start the service, either by using the IntelliJ run configuration run application (local-dev) or using maven (you need the dev-profile to connect to the local dev environment):

   ./mvnw spring-boot:run -Dspring-boot.run.profiles=dev
   

Quirks

• Testcontainers requires a lower API version than the current minimum requested by Docker 29. (Spring boot dependencies have a workaround, but this could break in the future - see #48104)

CI/CD Pipeline

The pipeline runs on all pushes to main and open merge requests:

1. Unit Tests - Runs unit tests, by calling mvn test
2. Semantic Release - Automatically determines version bumps and generates changelogs based on commit messages
3. Containerize - Builds and pushes Docker images to the GitLab registry

Versioning & Releases

Versions follow semantic versioning (Major.Minor.Patch). The pipeline analyzes commit messages since the last release to determine the version bump. Only the highest-priority change triggers a bump (e.g., 10 fixes + 2 features = 1 minor version bump).

Commit message keywords:

Important: Releases only happen on main. Merge request pipelines run in dry-run mode to preview the next version.

Docker Images

Images are tagged differently based on context:

• Releases: <version> and latest
• Main branch changes: <commit-sha>
• Merge requests: SNAPSHOT-<commit-sha>

Gitlab Dependency Proxy

The pipeline uses GitLab’s Dependency Proxy to cache docker images and prevent pull rate limits from docker hub. The base image eclipse-temurin:21 requires authentication, which is handled in the dependency proxy settings of the organization. We have a docker hub account registered under th-koeln@innovation-hub.de / thkarchilab. You can use the credentials with the variables $CI_DEPENDENCY_PROXY_USER and $CI_DEPENDENCY_PROXY_PASSWORD.

Metrics implemented

Below you can find the metrics as they show up in Prometheus (_ instead of .)