canonical / dex-auth-rocks

ROCKs for dex-auth
Apache License 2.0
0 stars 0 forks source link

Rocks from `main` and `track/2.36` are not published #22

Open DnPlas opened 1 week ago

DnPlas commented 1 week ago

Bug Description

It looks like the latest container images for these branches are not published correctly.

In main, the image was not published due to an error with the on_push CI (see here). This means that the latest change to the rockcraft project in dex did not created a charmedkubeflow/dex:2.39.1-bed284a image, which is inconsistent with the model we are following (having a tag per latest commit that changed the rockcraft project). To solve this we should re-run the build and publish CI from main.

In track/2.36, the image hasn't been published from the track branch, which is also inconsistent with the tagging model. To solve this we would have to update the rock from track/2.36 that triggers a build and publish job.

To Reproduce

  1. Check the tags of the published images in https://hub.docker.com/r/charmedkubeflow/dex/tags
  2. Check the latest commit hashes in main and track/2.36
  3. Observe the differences

Environment

No env

Relevant Log Output

No output

Additional Context

No response

syncronize-issues-to-jira[bot] commented 1 week ago

Thank you for reporting us your feedback!

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

This message was autogenerated