Proposal: adoption of pipelines-as-code

[vdemeester]

TL;DR: adoption of pipelines-as-code in the tektoncd org (https://pipelinesascode.com/).

The pipelines-as-code propose an opinionated CI based on OpenShift Pipelines / Tekton. Its goal is to let you define your Tekton templates inside your source code repository and have the pipeline run and report the status of the execution when triggered by a Pull Request or a Push.

Some notably features of pipelines-as-code:

• Pull-request status support: When iterating over a Pull Request. Statuses and Control is done on GitHub.
• GitHub Checks API support to set the status of a PipelineRun including rechecks
• GitHub Pull Request and Push event support
• Pull-request “GitOps” actions through comments with /retest, /test and so on.
• Automatic Task resolution in Pipelines (local Tasks, Tekton Hub, and remote URLs) — Note: This predates tektoncd/pipelines resolvers, and will slowly but surely be replaced by built-in resolvers as users will adopt those resolvers.
• Efficient use of GitHub blobs and objects API for retrieving configurations
• Git events Filtering and support for separate pipelines for each event
• Gitlab, Bitbucket Server, Bitbucket Cloud and GitHub Webhook support.
• tkn-pac plug-in for Tekton CLI for managing pipelines-as-code repositories and bootstrapping.

It is currently shipped with OpenShift Pipelines but it is released independently. It is also working and tested on vanilla kubernetes and has nothing OpenShift specific in the code.

The proposal is to have pipelines-as-code hosted and maintained by the community, and help shape the next set of Tektoncd components.

Who will own it

• @chmouel
• @sm43
• @savitaashture
• [any other takers]

[vdemeester]

/kind feature
/cc @afrittoli @bobcatfish @lbernick @abayer @jerop @dibyom @priyawadhwa

[abayer]

I'm all in favor!

[lbernick]

I'm very excited about this as well! I created a doc comparing our goals for workflows with pipelines as code (join tekton-dev google group to view + comment).

[bendory]

I like this approach too; as a general statement, it looks like the projects are more convergent than divergent, and the areas of divergence appear surmountable.

[lbernick]

I've opened #936 proposing adopting Pipelines as Code. Please take a look if you're interested!

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vdemeester]

@afrittoli @abayer @JeromeJu @jerop @dibyom @wlynch I would love to re-open this to discussion.
The main requirement we have today is, it's heavily use in production already, meaning, we consider the API as relatively stable, and any huge refactoring would need to happen targeting a v2 or something.

cc @chmouel, wdyt ?

One thought we had was, to setup pipelines-as-code on a cluster (maybe dogfooding or somewhere else), hook it up to a repository under tektoncd organiziton (for example tektoncd/cli) and showcase its possible usage within the org. If the experiments turns out to be a success, we could define what would be next.

[chmouel]

yes the refactoring could be quite a lot of work (ie: ~ 6 months) if we were planning a rewrite,

i'll be happy to help setup pac as demo to show how this could works on one of the tektoncd/ repos