This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch UNOMI-979-scheduler-lock-lease
in repository https://gitbox.apache.org/repos/asf/unomi.git
The following commit(s) were added to refs/heads/UNOMI-979-scheduler-lock-lease
by this push:
new 3ed33ce98 UNOMI-979: Skip unit tests in the integration-test CI jobs
3ed33ce98 is described below
commit 3ed33ce9805c9faf9e2bff53c73fa9335ecfa02f
Author: Serge Huber <[email protected]>
AuthorDate: Mon Aug 17 20:16:41 2026 +0200
UNOMI-979: Skip unit tests in the integration-test CI jobs
The unit-test job already runs the whole unit suite on the commit, and then
both
integration-test legs ran it again as part of their build before reaching
the
integration tests they exist for -- three executions of the same suite per
CI
cycle, two of them with no signal the first did not already give.
Both legs now pass --skip-unit-tests, an option build.sh already supports
and
documents alongside --integration-tests. It activates the skip-unit-tests
profile, which sets maven-surefire-plugin's skip only:
maven-failsafe-plugin is
untouched, so the integration tests themselves still run.
Measured on the full reactor (same 60 modules, same stop point, only
surefire
differing): 215.6s with unit tests versus 48.8s without, so roughly 2.8
minutes
of unit-test execution -- including the 806-test services module -- on a
16-core
machine. The CI runners have 2 vCPU, so the saving there is larger; the
unit-test job spends 10 minutes on build plus tests in total.
Unit-test regressions still fail the build: they fail it in the unit-test
job,
on the same commit, which is where that signal belongs.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
---
.github/workflows/unomi-ci-build-tests.yml | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/unomi-ci-build-tests.yml
b/.github/workflows/unomi-ci-build-tests.yml
index ebb283fef..febf15c73 100644
--- a/.github/workflows/unomi-ci-build-tests.yml
+++ b/.github/workflows/unomi-ci-build-tests.yml
@@ -143,11 +143,15 @@ jobs:
MAVEN_EXTRA_OPTS: >-
-Dopensearch.port=${{ matrix.port }}
-Delasticsearch.port=${{ matrix.port }}
+ # --skip-unit-tests: the unit-tests job above already ran them on this
same commit, and
+ # both IT legs would otherwise run the whole suite a second and third
time before getting
+ # to the integration tests they exist for. The flag activates the
skip-unit-tests profile,
+ # which sets surefire's skip only -- failsafe, and therefore the ITs,
still run.
run: |
if [ "${{ matrix.search-engine }}" = "opensearch" ]; then
- ./build.sh --ci --integration-tests --use-opensearch
+ ./build.sh --ci --integration-tests --skip-unit-tests
--use-opensearch
else
- ./build.sh --ci --integration-tests
+ ./build.sh --ci --integration-tests --skip-unit-tests
fi
# Keep only third-party dependencies in the post-job Maven cache:
Unomi's own
# snapshots are rebuilt every run and would only bloat the cache / risk
staleness
