Test-infra: Update tekton pipelines to enable working with v1beta1

Created on 10 Apr 2020 · 7Comments · Source: kubernetes/test-infra

Tekton pipelines have recently moved from v1aplha1 to v1beta1.

Prow currently assumes pipeline specs in prow job are v1alpha1 and using a v1beta1 spec is not possible.

This issue should track tasks to be done in order to allow using Prow with different Tekton pipelines versions.

Implementation should take care of existing Prow jobs and provide a smooth transition path.

From the top of my head, list of things to do:

[ ] Update tekton client code gen to support v1beta1 (https://github.com/kubernetes/test-infra/pull/17181)
[ ] Detect supported pipeline versions in the pipeline controller
[ ] Add support for pipeline version in pipeline controller
[ ] Add support for multiple pipeline version in Prow jobs

If you think about something else, please comment, i will update the PR description.

areprow kinfeature lifecyclrotten

Source

eddycharly

👀10

Most helpful comment

@harshad16 and I would be happy to test this out on OpenShift ;)

goern on 29 Jul 2020

👍4

All 7 comments

/assign

eddycharly on 10 Apr 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 9 Jul 2020

/remove-lifecycle stale

goern on 10 Jul 2020

@eddycharly Do you plan to pick this back up? I have a working branch of v1beta1 which includes some of your changes, I'm looking for the best way to move this forward. Were you planning to support both initially?

mikesplain on 23 Jul 2020

@harshad16 and I would be happy to test this out on OpenShift ;)

goern on 29 Jul 2020

👍4

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 26 Nov 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 26 Dec 2020

Was this page helpful?

0 / 5 - 0 ratings