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

Automatically execution of unittests on each GitHub Pull Request #2

Open
DylanVanAssche opened this issue Apr 16, 2024 · 0 comments
Open
Labels
data-generator Issues related to KROWN's data-generator enhancement New feature or request execution-framework Issues related to KROWN's execution framework

Comments

@DylanVanAssche
Copy link
Contributor

DylanVanAssche commented Apr 16, 2024

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

  • Fedora 39
  • KROWN 1.0.0
@DylanVanAssche DylanVanAssche added enhancement New feature or request execution-framework Issues related to KROWN's execution framework data-generator Issues related to KROWN's data-generator labels Apr 16, 2024
@DylanVanAssche DylanVanAssche moved this to Planned in Roadmap Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-generator Issues related to KROWN's data-generator enhancement New feature or request execution-framework Issues related to KROWN's execution framework
Projects
Status: Planned
Development

No branches or pull requests

1 participant