Skip to content
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

Enable tekton/openshift pipelines prow integration #2462

Closed
VannTen opened this issue Sep 2, 2022 · 7 comments
Closed

Enable tekton/openshift pipelines prow integration #2462

VannTen opened this issue Sep 2, 2022 · 7 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@VannTen
Copy link
Contributor

VannTen commented Sep 2, 2022

Prow apparently has the capacity to use tetkon pipelines as ProwJob (
see
https://pkg.go.dev/k8s.io/test-infra/prow/config#JobBase (PipelinRunSpec)
kubernetes/test-infra#13874
)

What can we do to enable that support ?

This would allow Apps developper to have composable CI pipelines, with reusable
Task notably.

(Prompted by #2320, #2320 (comment) in particular)

/kind feature

possible alternatives:

@Gregory-Pereira
Copy link
Member

/assign
I will help you look into this.

@Gregory-Pereira
Copy link
Member

Gregory-Pereira commented Sep 3, 2022

Seems that they currently dont have official documentation but have the steps documented unofficially see here: kubernetes/test-infra#13874 (comment).

To start review what work has already been done on this (see Christoph's initial implementation commit)

@Gregory-Pereira
Copy link
Member

Gregory-Pereira commented Sep 3, 2022

Blocked by prow kicking the bucket (ba dum tsss) 🪣 .
/lifecycle frozen

@sesheta sesheta added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 21, 2022
@durandom durandom transferred this issue from operate-first/apps Sep 21, 2022
@durandom durandom transferred this issue from operate-first/support Sep 21, 2022
@sesheta
Copy link
Member

sesheta commented Dec 20, 2022

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.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 20, 2022
@VannTen
Copy link
Contributor Author

VannTen commented Jan 9, 2023

/remove-lifecycle stale

@sesheta sesheta removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 9, 2023
@VannTen
Copy link
Contributor Author

VannTen commented Jan 18, 2023

/assign

@Gregory-Pereira
Copy link
Member

Closing as op1st is being decomissioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants