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

Containerize integration tests and development #2329

Open
pav-kv opened this issue Feb 5, 2021 · 0 comments
Open

Containerize integration tests and development #2329

pav-kv opened this issue Feb 5, 2021 · 0 comments

Comments

@pav-kv
Copy link
Contributor

pav-kv commented Feb 5, 2021

Scripts in integration/ are hard to maintain, and contain bugs. For example, after running run_integration.sh there are dangling Trillian servers.
Also, a developer needs to install tooling that exactly corresponds to Trillian CI (MySQL, Go, etc), which is sometimes not easy to do.

Running Trillian locally is much easier using Docker[-compose]. Most CI providers support containers anyway. We can make it possible to run Trillian locally in exactly the same state as in CI, using containers.

https://www.docker.com/blog/containerize-your-go-developer-environment-part-1/

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