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

Support Running pipelinerun explicitely/manually

XMLWordPrintable

    • 12
    • False
    • None
    • False
    • SECFLOWOTL-116 - On Comment and Chatops Support for Triggering PAC Pipeline
    • Hide
      Users now have the ability to explicitly start a PipelineRun using the /test <pipelinerun-name> comment, irrespective of whether the pipelinerun matches the annotations. This feature grants users explicit control over the execution of PipelineRuns for specific types of Pull Requests, allowing manual initiation instead of relying solely on events.

      This is particularly useful for scenarios where users need fine-grained control over the testing process, such as for Pull Requests managed by users rather than events.
      Show
      Users now have the ability to explicitly start a PipelineRun using the /test <pipelinerun-name> comment, irrespective of whether the pipelinerun matches the annotations. This feature grants users explicit control over the execution of PipelineRuns for specific types of Pull Requests, allowing manual initiation instead of relying solely on events. This is particularly useful for scenarios where users need fine-grained control over the testing process, such as for Pull Requests managed by users rather than events.
    • Pipelines Sprint 255, Pipelines Sprint 256, Pipelines Sprint 257, Pipelines Sprint 259, (temp)Backlog from 260 and 259

      Story (Required)

      As a user i would like to run a pipelinerun explicitly with gitops comments on my pull request even if there is no match on annotations or cel or otherwise...

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

            cboudjna@redhat.com Chmouel Boudjnah
            cboudjna@redhat.com Chmouel Boudjnah
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: