3 ms·
How do you handle very complex and integrated architectures like a monorepo with many microservices? How do you run your layer file locally? Can you describe
by gravypod 7y ago
How do you handle very complex and integrated architectures like a monorepo with many microservices?
How do you run your layer file locally?
Can you describe automated tests in a layer file?
I built something similar[0] to this for integration testing and those were my biggest hurdles. At a previous job where all of the code was python/node/java I was also able to generate cross-service end to end code coverage from these tests and that feature was extremely helpful as it helps you remove redundant tests.
Your service looks very polished and I'm extremely impressed someone is taking this idea to market.
0- bunt.build
- colinchartier 7y ago> monorepo with many microservices We scan the entire repository for Layerfiles, so you could, say, create a layerfile per service for unit tests, and a bigger Layerfile in the repo root that does the whole deployment and runs a few E2E tests. > How do you run your layer file locally? They can be approximated by running a docker container and just copy/pasting the commands. We haven't built this yet because I know it will be a huge time sink to make it reliable (see, e.g., vagrant) > Can you describe automated tests in a layer file? We tell you if any step fails (e.g., returns non-zero exit code) so you can just as easily run "./deploy.sh" as "./test.sh" - you can also start a webserver and run E2E or acceptance tests against it, for example. > generate cross-service end to end code coverage We are trying to avoid anything that isn't very general - it's possible to run https://codecov.io/ https://codecov.io/ within Layer if you want functionality like this.