forked from continuwuation/continuwuity
Sebastian Spaeth
bf6783cb83
Some checks failed
Documentation / Build and Deploy Documentation (push) Has been skipped
Mirror Container Images / mirror-images (push) Failing after 1m38s
Checks / Prek / Pre-commit & Formatting (push) Successful in 2m40s
Checks / Prek / Clippy and Cargo Tests (push) Successful in 12m33s
Release Docker Image / Build linux-amd64 (release) (push) Failing after 17m7s
Maintenance / Renovate / Renovate (push) Failing after 57s
Release Docker Image / Build linux-arm64 (release) (push) Failing after 15m7s
Release Docker Image / Create Multi-arch Release Manifest (push) Has been skipped
Release Docker Image / Build linux-amd64 (max-perf) (push) Has been skipped
Release Docker Image / Build linux-arm64 (max-perf) (push) Has been skipped
Release Docker Image / Create Max-Perf Manifest (push) Has been skipped
Release Docker Image / Mirror Images (push) Has been skipped
When running the mirror-images step from within the release-image workflow we receive error messages such as > msg="Failed to sync" target=ghcr.io/continuwuity/continuwuity:v0.5.0-rc.7 > source=forgejo.ellis.link/continuwuation/continuwuity:v0.5.0-rc.7 > error="failed to send blob post, ref > ghcr.io/continuwuity/continuwuity@sha256:74976f7b85018b5abd867333bc783c7230d985a4b0af595bbf55964e25afe6ef: > unauthorized" So, we will need to define our credentials in the release-image workflow too it seems, when we pull in the mirror-image workflow. This is a test by adding all credentials that are defined in mirror-images.yml Probably we don't need them all, but if this does not work, the whole approach is flawed and we can remove everyting again. If it works, we should remove unneccessary credentials until we found the required ones. |
||
|---|---|---|
| .. | ||
| actions | ||
| regsync | ||
| workflows | ||
| pull_request_template.md | ||