Why branch pipeline run persists in Bitbucket under pipeline section

[vinoth_vinothkumaar_accenture]

For Apigee Centralized setup we have done the below things via bitbucket pipeline,

• Centralized pipeline has been separated to break out Spectral Linter, Sonar Scan, and Deployment into independent steps.

• Step-level reporting has been implemented — results for each step are posted back to the child pipeline individually.

• Scenario 1 (PR from feature/test → develop) for Proxy:

  • Only Spectral Linter and Sonar Scan are executed.

  • Child pipeline output correctly shows 2 steps.

• Scenario 2 (Merge to develop) for Proxy:

  • Spectral Linter, Sonar Scan, and Deployment are executed.

  • Child pipeline output correctly shows 3 steps.

• Fail-fast behavior is enforced: if a step fails, subsequent steps are skipped and failure is reported back to the child pipeline.

• Verified that Sonar dashboard reflects the correct feature/* branch name during PR scans to avoid confusion.

Similarly for Sharedflow and Config repos as well the centralized pipeline setup is completed and spectral linter step alone will be skipped.

Now developers are requesting to expect the same scenario 1 as above using the Run Pipeline option in the Pipelines tab where they are trying to run the pipeline via pipelines tab and selecting the branch as feature/test and pipeline as branches: develop

Why we have 2 options (PR based and Run pipeline) to run the pipeline in bitbucket?