fix: Fix archetype tests in CI - #1259
Merged
Merged
Conversation
CharlesDuboisSAP
approved these changes
Aug 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
A new archetype (spring-boot4) got added recently. Unfortunately, that caused a degradation in the CI pipeline:
The build job of the CI pipeline runs Maven with
--threads 1C(multi-threaded) and thus both archetype modules write to the shared~/.m2/repository/archetype-catalog.xmlduringmvn install. This causes a race condition where one archetype's entry can overwrite the other's, leaving the catalog with potentially only one entry. The test-archetypes job then fails with "Specified archetype not found" for spring-boot3 — seemingly randomly depending on thread scheduling. (See for example here.)Additionally, the new archetype spring-boot4 is never tested in in the CI pipeline.
This PR addresses both issues by building the archetypes sequentially and adding the new archetype to the test matrix.
Successful CI run with the new setup here.