-
Notifications
You must be signed in to change notification settings - Fork 110
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
Release pipelines should pin their image versions #2197
Comments
Dashboard and Pipelines nightly releases are passing again, updated to use the latest Andrea also has a PR open against Triggers to update it to the latest PRs open for other projects, custom tasks, interceptors, etc. to pin images to known working state. |
Triggers nightly release is passing again, also updated to the latest The following nightly releases are also passing again:
Chains nightly is failing due to a known bad test: tektoncd/chains#1178
|
This is now working fine, I fixed the references to the wrong tasks.
This now failing for the same
This now fails with a PR to fix: #2225 |
Related to: tektoncd#2197 Signed-off-by: Andrea Frittoli <[email protected]>
Fix for the CEL component: tektoncd/experimental#979 |
Related to: #2197 Signed-off-by: Andrea Frittoli <[email protected]>
Remaining issues:
|
All remaining issues have been fixed. |
Thanks for seeing this over the line @afrittoli 🙇 I'll be back next week |
All nightly releases started failing on September 19th due to an issue with the
koparse
image, see fix in #2196The nightly releases picked up the bad image as they were using the
latest
tag.All images should be pinned using an appropriate image digest to ensure repeatable builds and to avoid picking up unexpected changes. From a quick review of the first few nightly releases many projects are using the
latest
tag of at least theko
,ko-gcloud
, andkoparse
images.List of releases in the
tekton-nightly
namespace:Taking the most recent one as an example, these are the unpinned images used, most are using
latest
:wait-task
The text was updated successfully, but these errors were encountered: