actions: use artifacts instead of registry for forks #7558
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #7549 we tried to fix CI for external contributors by using the fork repo registry instead of the base repo registry. Unfortunately GITHUB_TOKEN cannot be used to write to the fork repo registry, it only has read access to the base repo registry.
Instead, use artifacts to pass around built Docker images.
Based on #7554 (but doesn't attempt to re-arrange the actions workflow).
There is quite a lot of boilerplate due to uploading/downloading/loading individual images. We could reduce that boilerplate by always uploading/downloading all images (at the cost of more time spent downloading stuff we won't use), or introducing a re-usable step in a separate yaml file.