ci: run no-database tests in parallel with database tests - #1860
Merged
Conversation
… critical path Signed-off-by: Marvin Froeder <velo.br@gmail.com>
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
1 participant
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.
compilepreviously ranclean install -Pno-databases, executing all database-independent tests on the critical path — every database test jobneeds: compileand had to wait for those tests before starting.Changes:
compilenow builds only (-DskipTests) and publishes the artifact cache — no tests.no-databasesjob runs the database-independent tests, restoring the cache, in parallel with the database test jobs.no-databasesto thebuildaggregate (the required status check).Net effect: the database jobs no longer wait on the unit-test suite, and the no-database tests run concurrently with them.