Use docker-compose stack for integration tests - #149
Merged
Merged
Conversation
Owner
|
docker-compose.yml should still be the full file name |
thatliuser
force-pushed
the
use-compose-for-integration
branch
8 times, most recently
from
September 13, 2026 20:07
92b418b to
b5795fb
Compare
thatliuser
force-pushed
the
use-compose-for-integration
branch
from
September 13, 2026 22:18
b5795fb to
cad6e12
Compare
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.
the integration test containers are hardcoded in the CI action and split from the makefile.
this pr makes the integration tests use compose stack containers in both cases (local & ci)