Pipeline condition changeset only takes last commit into account

Cristian Lopez_r5fzvh

Hello team!

 

currently we are facing a weird behavior. Although the documentation says that all commits are taken into account when evaluating the pull request files, it is currently using only the last commit.

 

I just figured this out because we use conditions for all our steps, after updated the bitbucket-pipelines.yml file, all steps were skipped (which does not make sense because several conditions passes). The way to get expected steps executed is to squash all pull request commits into one.

 

Sorry if this is not the best place to ask / report.

Norbert Csupka

Hi Cristian,

Thank you for contacting Atlassian Community, my name is Norbert and I'm a Bitbucket Cloud Support Engineer, it's nice to meet with you! Welcome to the Atlassian Community!

I would like to inform you that this is a good place to ask/report.

Can you let me know what's in your bitbucket-pipelines.yml configuration, please? With this configuration which I have, the builds were executed correctly and even the previous commits were taken into account:

image: atlassian/default-image:3

pipelines:
pull-requests:
'**': #this runs as default for any branch not elsewhere defined
 - step:
script:
 - echo "test"
condition:
changesets:
includePaths:
 - "potato/*.xml"

 Please let us know, we're here to help.

Best Regards,
Norbert
Atlassian Bitbucket Cloud Support