Andrew Bayer
Andrew Bayer
# Changes We will reject anything that doesn't start with `git://`, `ssh://`, `https://`, or `/`. The last is for use in our own tests, and is not included in the...
Relates to #4710 With remote resolution coming out of `alpha` in v0.41.0, the legacy `taskRef.bundle` and `pipelineRef.bundle` syntax should be deprecated in favor of using the `bundles` resolver.
Prompted by https://github.com/tektoncd/pipeline/pull/5405#discussion_r959932866 The error that gets returned to the `ResolutionRequest` reconciler when the relevant resolver hits an error fetching the resource is a bit ugly: ``` error getting "Cluster"...
Prompted by https://github.com/tektoncd/pipeline/pull/5405#discussion_r959924196 Right now, we require that you explicitly specify a `kind` parameter for most remote resolvers (`hub`, `bundle`, the new `cluster` one added in that PR, though not...
# Changes This will be used as part of https://github.com/tektoncd/plumbing/issues/483 in Tekton's own CI setup, and I think it could be generally useful for replicating behavior such as Prow's job...
I believe #57 is better - it avoids the erstwhile deprecated path completely, at the cost of having to run `docker login ...` once for each of `gcr.io`, `us.gcr.io`, `eu.gcr.io`,...
# Expected Behavior `Pipeline` validation should fail at creation time when a matrix parameter is set to an empty array. # Actual Behavior The `PipelineRun` reconciler will panic when attempting...
# Changes fixes #5925 /kind feature # Submitter Checklist As the author of this PR, please check off the items in this checklist: - [x] Has [Docs](https://github.com/tektoncd/community/blob/main/standards.md#docs) included if any...
...which is resulting in `tekton-pipelines-webhook` log lines like: ``` {"severity":"error","timestamp":"2023-01-30T21:07:19.462Z","logger":"tekton-pipelines-webhook","caller":"conversion/conversion.go:59","message":"Conversion failed","commit":"6db52ca","uid":"8d0e7396-74dd-42a4-ac67-842332b180f3","desiredAPIVersion":"resolution.tekton.dev/v1alpha1","error":"conversion failed to version v1alpha1 for type [kind=ResolutionRequest group=resolution.tekton.dev version=v1beta1] - v1beta1 is the highest known version, got: *v1alpha1.ResolutionRequest","stacktrace":"knative.dev/pkg/webhook/resourcesemantics/conversion.(*reconciler).Convert\n\tknative.dev/[email protected]/webhook/resourcesemantics/conversion/conversion.go:59\nknative.dev/pkg/webhook.conversionHandler.func1\n\tknative.dev/[email protected]/webhook/conversion.go:66\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2084\nnet/http.(*ServeMux).ServeHTTP\n\tnet/http/server.go:2462\nknative.dev/pkg/webhook.(*Webhook).ServeHTTP\n\tknative.dev/[email protected]/webhook/webhook.go:263\nknative.dev/pkg/network/handlers.(*Drainer).ServeHTTP\n\tknative.dev/[email protected]/network/handlers/drain.go:113\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:2916\nnet/http.(*conn).serve\n\tnet/http/server.go:1966"} ```...
The ones I notice right now are the `plumbing-image-build` and `pull-pipeline-kind-k8s-v1-21-e2e` PR `PipelineRun`s, and the `build-and-push-test-runner` cronjob triggered `PipelineRun`. I've seen the `test-runner` image builds cause OOMs on their nodes,...