-
Notifications
You must be signed in to change notification settings - Fork 166
Update on-cluster build docs to use Tekton 1.6.0 #3194
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
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: creydr The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3194 +/- ##
==========================================
+ Coverage 51.81% 51.82% +0.01%
==========================================
Files 162 162
Lines 19131 19131
==========================================
+ Hits 9912 9914 +2
+ Misses 8241 8240 -1
+ Partials 978 977 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/hold |
|
very strange 'reset by peer' errors across PRs currently on top of some 'no space left on device' suddently |
|
Maybe reabase on |
Tekton images have been moved from gcr.io to ghcr.io (see github.com/tektoncd/pipeline/issues/8870#issuecomment-3057843599). Using the old manifests leads failing image pulls nowadays. Therefor updating to the latest Tekton manifests.
cb8f046 to
8a776ce
Compare
Tekton images have been moved from gcr.io to ghcr.io (see tektoncd/pipeline#8870). Using the old manifests leads failing image pulls nowadays. Therefore updating to the latest Tekton manifests.