Conversation
| args: | ||
| ubuntu_version: "bionic" | ||
| swift_version: "5.1" | ||
| swift_version: "5.1.3" |
There was a problem hiding this comment.
this means we would need to keep this up to date as minor revisions are released
There was a problem hiding this comment.
@tomerd Yes. Is there another way to force the CI to pull the latest 5.1?
There was a problem hiding this comment.
the issue here is that docker will catch the 5.1 image (the tag. latest is a special case), so the only way would be to forcibly invalidate the cache which is not ideal
There was a problem hiding this comment.
Right. I think manually bumping is fine for now. Or we implement something where it’d kill the cache once a week or so?
There was a problem hiding this comment.
yes we can do that. we can also create a CI job that will nuke the relevant cache for a specific version. this may be part of the checklist when we release new versions?
No description provided.