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

OpenShift Pipelines As Code is not working with on-path-change in Bitbucket Data Center

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Before this update, a push PipelineRun with the `on-path-change` annotation was not triggered on pull request merge events, even when the merged pull request modified the paths specified in the annotation. This update resolves that issue, ensuring that the pipeline is correctly triggered when relevant path changes are introduced via a pull request merge.
      Show
      Before this update, a push PipelineRun with the `on-path-change` annotation was not triggered on pull request merge events, even when the merged pull request modified the paths specified in the annotation. This update resolves that issue, ensuring that the pipeline is correctly triggered when relevant path changes are introduced via a pull request merge.
    • Enhancement
    • Done
    • Pipelines Sprint Crookshank 31

      Description of problem:

      While doing Merge PullRequest, PAC not able to trigger PipelineRun for event push with `on-path-change` on Bitbucket-Server/DataCenter. In logs it does say Push event but cannot find matching PipelineRun.

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

      Steps to Reproduce

       - Setup Bitbucket Server/DataCenter with PAC

      • Configure two pipelineRun with on-path-change and with same directories
      • First PipelineRun will have target branch as xyz and Second have target branch as main/master
      • Make changes to xyz and create a pull request with main/master branch.
      • This will trigger first PipelineRun.
      • Merge Pull Request to Main/master branch.

       

      slack thread: https://redhat-internal.slack.com/archives/CSPS1077U/p1743998168167349

      Actual results: push event PipelineRun doesn't get trigger with logs 

      **

      "msg":"cannot match the event to any pipelineruns in the .tekton/ directory, payload target event is push with source branch refs/heads/master and target branch refs/heads/master. 

      Expected results: Trigger second PipelineRun

      Reproducibility (Always/Intermittent/Only Once): Always

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

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

      Please note this did work until adding the annotations for pipelinesascode.tekton.dev/on-path-change: 

       *

              rh-ee-zashaikh Zaki Shaikh
              rhn-support-sburhade Satyam Burhade
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: