What's happening?
Each change inside a Pull Requests requires running KROWN's execution framework unittests manually because they require running Docker containers inside Docker containers because the CI/CD setup itself is a Docker container. This imposes some challenges to perform this automatically on each Pull Request.
What's supposed to happen?
On each Pull Request all unit tests are executed by a GitHub CI/CD setup to verify if we haven't broken anything.
KROWN's data generator does not have this limitation, but we want to tackle this issue together to have a single CI/CD setup.
Environment
What's happening?
Each change inside a Pull Requests requires running KROWN's execution framework unittests manually because they require running Docker containers inside Docker containers because the CI/CD setup itself is a Docker container. This imposes some challenges to perform this automatically on each Pull Request.
What's supposed to happen?
On each Pull Request all unit tests are executed by a GitHub CI/CD setup to verify if we haven't broken anything.
KROWN's data generator does not have this limitation, but we want to tackle this issue together to have a single CI/CD setup.
Environment