Repository navigation
fix(minio): point MinIO image references to Quay, retiring it from CI matrix - #3932
Conversation
✅ Deploy Preview for testcontainers-go ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@copilot the image you chose is protected by login:
We probably need a way to skip that from CI |
Co-authored-by: mdelapenya <951580+mdelapenya@users.noreply.github.com>
Confirmed: anonymous pulls of this Quay repository return 401, so the current PR does not restore the MinIO job. Skipping MinIO in CI would disable the failing tests and broaden the requested image-only scope. Would you like us to change the scope to skip the MinIO job, or use an approved publicly pullable image for this release instead? |
|
@copilot, as you working in skipping minio from CI? ALso add a note in the docs regarding the required login for the minio image |
Co-authored-by: mdelapenya <951580+mdelapenya@users.noreply.github.com>
The MinIO integration job fails while pulling
minio/minio:RELEASE.2024-01-16T16-07-38Zfrom Docker Hub, before either test can start a container.RunContainerdefault,TestMinio,ExampleRun, and the matching docs example to usequay.io/minio/miniowith the same release tag.