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

glob pattern with on cel expression for pathChanged() does not behaves expected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • None
    • Pipelines as Code
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Pipelines Sprint 257

      Description of problem:

      PAC does not trigger the pipeline as expected on the basis of glob pattern pathChanged().

      annotations:
          pipelinesascode.tekton.dev/on-cel-expression: |
            event == "push" && target_branch == "preview-POCPromotionToProd" &&
            (
              "components/?*/base/**".pathChanged()
            )
      

      As per the glob pattern `"components/?/base/".pathChanged()` ** the pipeline should only get triggered when changes in the file for ex- components/<dummy-path>/base/<dummy-path>/<dummy-path>

      but it should not get triggered when components/<dummy-path>/<dummy-path>/base/<dummy-path> file change.

      I have also tried verifying the pattern

      However when I am using the same its not working as expected with PLR

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      • Create a PLR with pathChanged() value includes the above explained scenario

      Actual results:

      Triggers the pipeline in either of the path change scenario

      • components/<dummy-path>/base/<dummy-path>/<dummy-path>
      • components/<dummy-path>/<dummy-path>/base/<dummy-path>

      Expected results:

      Pipeline should only be triggered when 

      • components/<dummy-path>/base/<dummy-path>/<dummy-path>

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       *

              sashture Savita .
              pkumari Priti Kumari (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: