-
Bug
-
Resolution: Unresolved
-
Critical
-
Pipelines 1.19.0, Pipelines 1.19.1, Pipelines 1.19.2, Pipelines 1.19.3
-
None
Description of problem:
The issue occurs when working with more feature branches on Bitbucket Server it's taking the last commit of the branch and not the merged result from the master branch.
can not fetch the current changes if the newest commit is a merge commit.
Do not receive the newest commit in {{ revision }} dynamic variable if the newest commit is a merge commit.
Prerequisites (if any, like setup, operators/versions): 1.19
Steps to Reproduce
- Update to OSP 1.19
- Use Bitbucket Server/DC for PAC
- Use Annotations:
pipelinesascode.tekton.dev/on-event: "[push]" pipelinesascode.tekton.dev/on-target-branch: "[refs/tags/*]"
- upload code, create pull request, and merge commit
- It triggers a PipelineRun
Actual results:
spec:
params:
- name: commit-id
value: "{{revision}}"
This param {{ revision }} gets last commit of the branch
Expected results:
spec:
params:
- name: commit-id
value: "{{revision}}"
This param {{ revision }} should get newly merged commit{}
Reproducibility (Always/Intermittent/Only Once): Always
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
*
- is caused by
-
SRVKP-7432 OpenShift Pipelines As Code is not working with on-path-change in Bitbucket Data Center
-
- Closed
-