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

Developer friendly interface to launch pipelines from git

XMLWordPrintable

    • False
    • None
    • False

      This Request for Enhancement proposes the development and integration of a new feature of OpenShift Pipelines within the OpenShift Console.

      1. Proposed title of this feature request

      Developer friendly interface to launch pipelines from git

      2. What is the nature and description of the request?

      We are seeking a user-friendly interface designed to enable users to run pipelines directly from source code repositories hosted on Git, with simple and user-friendly input of pipeline parameters and without the prerequisite of these pipelines being already present as Custom Resource Definitions (CRDs) within the cluster.

      This interface aims to streamline the process of executing pipelines, particularly for those that are managed as code in Git repositories and have not been created as pipeline resources on the cluster, by providing a simplified mechanism for parameter entry and execution initiation. This would enable us to migrate more pipeline workflows from Jenkins to OpenShift Pipelines without harming user experience.

      For Pipelines that already exist as CRD’s on a cluster, OpenShift provides user-friendly graphical interfaces for starting pipelines and supplying parameters. We would like a similar interface when using pipelines as code (https://pipelinesascode.com).

      3. Why does the end customer need this? (List the detailed business requirement here)

      To complete a migration from Jenkins to OpenShift Pipelines and offer comparable user experience to end users. Jenkins has developer friendly user interfaces to allow users to launch pipelines that are defined in git with additional parameters.

      Currently OpenShift Pipelines only allows supplying parameters in json format when launching a Pipeline defined only in git (i.e. not existing on the cluster as a Pipeline resource). This is not user friendly.

      4. How would the customer like to achieve this? (List the functional requirements here)

      Developers can create a pipeline run from the Openshift console by entering/selecting parameters from a drop down list for the run
      Pipeline run should reference a git sourced pipeline resource

      5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

      • Developers can create a pipeline run from Openshift console by entering/selecting parameters from a drop down list for run

      Have a section on the openshift console for creating pipeline runs.
      These could be filtered by label, These should have RBAC on them
      Create desired pipeline run and select from a pre-canned drop down list and free text field, Results of this run are visible in the console.

      • Pipeline run should reference a git sourced pipeline resource

      Ensure pipeline resource is only available via git ie git referenced.
      Make these available during a pipeline run creation via the console

      6. Does the customer have any specific timeline dependencies and which release would they like to target?
      No hard deadlines on this.

      7. List any affected packages or components.
      Openshift console
      Tekton

      8. Would the end customer be able to assist in testing this functionality if implemented?
      Yes, we are available for testing

            Unassigned Unassigned
            rhn-support-dkarde Dipak Karde
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: