Support Tekton pipeline definitions in GitLab

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Users who are interested in portability between their CI pipelines definition see two open-source DSLs for doing so. GitLab CI/CD YAML and Tekton Pipelines (an extension of Kubernetes Custom Resources). Today they don't have any assurance of portability between GitLab and tools which support Tekton (OpenShift, Jenkins X and Google Tekton Pipelines)

Intended users

• Devon (DevOps Engineer)
• Allison (Application Ops)

Proposal

I'd propose the following multi-step process for support:

• - First iteration - test the portability between the two languages today. Many of the constructs in both (pipelines, jobs/tasks, images, scripts) are similar. The porting might be easily accomplished. Use this as an opportunity to assess the maturity of Tekton pipeline definition.
• - Second iteration - GitLab community engage and influence the DSL in Tekton pipelines to ensure portability remains.
• - Third iteration - Enable a lightweight Tekton pipeline interpreter so that Tekton pipeline definitions placed in your GitLab repository could be consumed and run by GitLab runners

Results

• Initial POC found that portability between the two DSLs is not straightforward.

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references