search

canonical / bundle-kubeflow

Charmed Kubeflow
Apache License 2.0
104 stars 50 forks source link

pin all shared rocks CI to releases and not `main` #784

Open ca-scribner opened 12 months ago

ca-scribner commented 12 months ago

Why it needs to get done

Presently, our rocks repos consume shared workflows by pinning to main (oidc, seldon). This is fine as we're fleshing these shared workflows out, but we should switch to pinning to releases once development on the shared workflows stabilises.

What needs to get done

Pin all calls to charmed-kubeflow-workflows workflows to a release

When is the task considered done

When all rocks repos use shared workflows that are pinned to a release, not main

syncronize-issues-to-jira[bot] commented 12 months ago

Thank you for reporting us your feedback!

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

This message was autogenerated

ca-scribner commented 8 months ago

One item to note here is that in the past even when we've pinned to a snap channel, we've been burned by broken CI later due to bugs or backwards incompatible changes. Ideally we'd want the option to pin to a specific revision

It would be really nice if we had automation to "release" a branch, and that would look at the current dependency versions (eg: rockcraft=latest/stable, which today is rev=123) and automatically pin those to today's revision