-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: add a job to sync 3rd party container images #546
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels liek too much text to accomplish what it is doing. Can we just iterate over a loop of images to sync ? (see inline comment).
I don't actually think this will help much to remove dependency on docker.io.
- We still have 'docker://' references in several tests
- we already were syncing these images to a local oci repo in the beginning of the build. That sync is still using docker:// even after ci: point docker registry to local copy #544, so c-i builds still depend on it.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #546 +/- ##
=======================================
Coverage 13.01% 13.01%
=======================================
Files 40 40
Lines 6003 6003
=======================================
Hits 781 781
Misses 5094 5094
Partials 128 128 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Ramkumar Chinchani <rchincha@cisco.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM -- Can you resolve your issues? Or were you wanting @smoser to reply?
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.