Skip to content

Allows overriding the BACKEND_ENDPOINT via env #73

Allows overriding the BACKEND_ENDPOINT via env

Allows overriding the BACKEND_ENDPOINT via env #73

# yamllint --format github .github/workflows/test.yml
---
name: test webflux5-sleuth
on:
# We deploy non-tagged pushes to master relevant for this project. We can't opt out of
# documentation-only commits because GH actions does not permit paths and paths-ignore.
pull_request:
branches: master
paths:
- "build-bin/**"
- "docker/**"
- "webflux5-sleuth/**"
- ".github/workflows/test-webflux5-sleuth.yaml"
- "parent-pom.xml"
jobs:
test:
runs-on: ubuntu-22.04 # newest available distribution, aka jellyfish
steps:
- name: Checkout Repository
uses: actions/checkout@v4
with:
fetch-depth: 1
- name: Cache local Maven repository
uses: actions/cache@v3
with:
path: ./m2repository # Shared with the Docker build context via .dockerignore
key: ${{ runner.os }}-webflux5-sleuth-maven-${{ hashFiles('parent-pom.xml', 'webflux5-sleuth/pom.xml') }}
restore-keys: ${{ runner.os }}-webflux5-sleuth-maven-
# Don't attempt to cache Docker. Sensitive information can be stolen
# via forks, and login session ends up in ~/.docker. This is ok because
# we publish DOCKER_PARENT_IMAGE to ghcr.io, hence local to the runner.
- name: Test webflux5-sleuth
run: |
build-bin/configure_test webflux5-sleuth &&
build-bin/test webflux5-sleuth