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:

• ci: Allow PRs from external forks to run (specific) workflows bundle-kubeflow#764
• Set Integration CI to run weekly for all repos #11 (but it is not so useful without Improve visibility of CI status, publishing status, etc, across our repos #134)
• Disable Juju's automatic retry for error'd events in CI for all repos  bundle-kubeflow#807
• Use very short names in our reusable workflows charmed-kubeflow-workflows#49

The rest:

• refactor how we build images in CI so we test the exact images that we ship bundle-kubeflow#766
• Standardize how our CI creates debug logs #125
• Clean up the pytest output during test/CI failure #129
• Improve visibility of failed publishing when merging to main or a track #130
• Enable pinning our CI build dependencies (ex: charmcraft) to specific revisions #133
• Improve visibility of CI status, publishing status, etc, across our repos #134
• Implement common CI workflows for all charm repositories charmed-kubeflow-workflows#50
• Enable pinning our charm test dependencies (ex: if kubeflow-dashboard's tests need to deploy kubeflow-profiles) #136
• Have CI to auto-promote charms to stable for changes in track branches bundle-kubeflow#901
• ci: Refactor multi-charm repos to run integration and unit tests only upon sub-directory changes bundle-kubeflow#931

Definition of Done

The issues have been resolved or postponed

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

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

This message was autogenerated