Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Integration tests] Move parts of the integration test infra to Test Containers hosted by GitHub runners #277

Closed
zarusz opened this issue Jul 1, 2024 · 3 comments
Assignees

Comments

@zarusz
Copy link
Owner

zarusz commented Jul 1, 2024

Provision an Azure-hosted VM to run containers for the build pipeline (integration tests).

Also soon the CloudKarafka hosting is coming to end of its life and we need to find a Kafka hosting replacement.
We could simply run Test Containers instead.

@zarusz zarusz self-assigned this Jul 1, 2024
@EtherZa
Copy link
Contributor

EtherZa commented Jul 3, 2024

@zarusz FYI: GitHub hosted runners come with Docker pre-installed.

GitHub sample
TestContainers

@zarusz
Copy link
Owner Author

zarusz commented Jul 3, 2024

Thanks for the find. I thought the default runners didn't support docker when I read it.

@zarusz zarusz changed the title [Integration tests] Provision self hosted runner to run Test Containers [Integration tests] Move parts of the integration tests run by GitHub runners to Test Containers Jul 3, 2024
@zarusz zarusz changed the title [Integration tests] Move parts of the integration tests run by GitHub runners to Test Containers [Integration tests] Move parts of the integration test infra Test Containers hosted by GitHub runners Jul 7, 2024
@zarusz zarusz changed the title [Integration tests] Move parts of the integration test infra Test Containers hosted by GitHub runners [Integration tests] Move parts of the integration test infra to Test Containers hosted by GitHub runners Jul 7, 2024
@zarusz
Copy link
Owner Author

zarusz commented Jul 7, 2024

Closed via #278 minus the caveat that Kafka will be moved to Test Containers after #110.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants