Tracker for issues against our charm repo CI

[ca-scribner]

Context

This tracks issues raised against our charm repo CI so we have a good starting point for broad fixes or changes. Any pain points that apply to the broader CI can be added here (but CI issues for specific repos is out of scope). This is similar to how canonical/bundle-kubeflow#765 tracks issues for rocks repo CI.

What needs to get done

Tackle the issues below:

Easy tasks:

• https://github.com/canonical/bundle-kubeflow/issues/764
• canonical/kubeflow-ci#11 (but it is not so useful without #134)
• https://github.com/canonical/bundle-kubeflow/issues/807
• canonical/charmed-kubeflow-workflows#49

The rest:

• https://github.com/canonical/bundle-kubeflow/issues/766
• canonical/kubeflow-ci#125
• canonical/kubeflow-ci#129
• canonical/kubeflow-ci#130
• canonical/kubeflow-ci#133
• canonical/kubeflow-ci#134
• canonical/charmed-kubeflow-workflows#50

• 136

• canonical/bundle-kubeflow#901
• canonical/bundle-kubeflow#931

Definition of Done

The issues have been resolved or postponed

[syncronize-issues-to-jira[bot]]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5289.

This message was autogenerated