You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in multi-charm repositories (e.g. KFP), we run the CI for every charm on every PR. This doesn't make sense when there are no changes to a charm's directory. The integration between them should be tested by the repo's bundle tests.
What needs to get done
Refactor multi-charm repositories to run integration and unit tests for each charm only when there is a change in their corresponding directories.
Definition of Done
Specific charm tests are run only when something changes.
The text was updated successfully, but these errors were encountered:
Context
Currently in multi-charm repositories (e.g. KFP), we run the CI for every charm on every PR. This doesn't make sense when there are no changes to a charm's directory. The integration between them should be tested by the repo's bundle tests.
What needs to get done
Refactor multi-charm repositories to run integration and unit tests for each charm only when there is a change in their corresponding directories.
Definition of Done
Specific charm tests are run only when something changes.
The text was updated successfully, but these errors were encountered: