Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-3862

Bootstrap a tekton "resource" repository or set of repository

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • Tekton Ecosystem
    • None
    • 3
    • False
    • None
    • False

      As a "MVP" (for the lack of a better term), we need a repository or a set of repository where we will maintain our tekton resources (task, pipeline, …)

      We need to decide wether we want one central repository for everything, or severela. The "challenge" is very similar to upstream.

      • One central repository means we are not using git for versionning (tagging, branching, …) but we copy/paste task over time.
      • Several repository under a specific org is more granular, allow us to use git versionning and group tasks/pipeline per context and version them together. For example, the go-build, go-test, … tasks can be versionned together.

      Once we agree on the solution to adopt, we need to create org, repositories, …

              vdemeest Vincent Demeester
              vdemeest Vincent Demeester
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: