Open ca-scribner opened 5 months ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5618.
This message was autogenerated
canonical/bundle-kubeflow#1005 discusses instability that feels related to this issue
Context
We've encountered a lot of instability in the kfp CI of late, including oddly flaky charmcraft builds for some of the charms. For some unknown reasons, standalone charmcraft seems to build things more reliably than building them in the pytest file directly using the pytest-operator.
Proposed here is that we move the building for these charms out of the pytest files and into their own jobs, then pass the .charm files as artifacts to the tests/publish jobs. This would hopefully add stability just from using charmcraft, but also we can have retry logic around failed build jobs (build jobs could auto-retry X times, so flakes could be mitigated)
What needs to get done
Definition of Done