ci(rocks): tracker to tackle issues we bump on often across our rocks repos

[orfeas-k]

Why it needs to get done

There are different issues we bump on with our rocks CI. This will act as a parent issue for everything that we need to fix in order to allow us to tackle those in an organized and focused way.

We need this order to eliminate issues in our rocks CI and construct a more hassle-free developer experience.

What needs to get done

Tackle all issues below:

Quick tasks:

• Update push and pull_request CI in ROCKs repositories #797
• Create documentation for reusable ROCKs CI charmed-kubeflow-workflows#47
• get-rocks-modified-and-build-scan-test-publish.yaml fails if no rocks need to be published charmed-kubeflow-workflows#43
• Use very short names in our reusable workflows charmed-kubeflow-workflows#49

The rest:

• build ROCKs in CI only once on every PR/push event charmed-kubeflow-workflows#28
• Standardize on_pull_request and on_push reusable workflows for ROCKs charmed-kubeflow-workflows#31
• rocks: publish jobs should not overwrite images with the same tag unless forced charmed-kubeflow-workflows#32
• rocks: publish jobs should append the git commit hash to an image's tag  charmed-kubeflow-workflows#35
• reduce duplication of rock image testing code across our repositories #783, Use a non-fixed image name in ROCKs tests and CI #785, and design and implement generic unit tests for all rocks #817
• pin all shared rocks CI to releases and not main #784
• Add integration tests to rock repos #816
• Skip building integration test environment when we have no rock integration tests charmed-kubeflow-workflows#46
• Create a spec for ROCKs CI charmed-kubeflow-workflows#48
• Add automation to charm repos to track their associated rock, warn if we are not using the latest rock kubeflow-rocks#77
• Create action that copies ROCK to Docker charmed-kubeflow-workflows#29

When is the task considered done

All issues above have either been resolved or we have decided to skip/postpone those.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

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

This message was autogenerated

[ca-scribner]

I've refactored this issue a little to track issues we face with our rocks CI. Issues for other CI are tracked in canonical/kubeflow-ci#124