Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,461,203
Community Members
 
Community Events
176
Community Groups

Pipeline condition changeset only takes last commit into account

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.

1 answer

1 accepted

0 votes
Answer accepted
Norbert C Atlassian Team Feb 21, 2022

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

Hi Norbert, nice to meet you too!

 

the configuration you asked is:

 

image: node:12.22.6

 

Thanks for checking

I have also check this doc piece, but didn't find anything relevant as we are just using an official image.

 

Let me know what other info can I provide to tackle this!

FYI - I have updated the main pipeline image to use the one in your example and did not fix the behavior (it is still using only the last commit, skipping all the steps)

Norbert C Atlassian Team Feb 22, 2022

Hi Cristian,

I've only received the image:XXXXXX part from your configuration, would it be possible for you to post the whole bitbucket-pipelines.yml file (masking the confidential information)? I'd like to review your configuration as it would help me figure it out, what could go wrong.

Thank you!

Best Regards,
Norbert
Atlassian Bitbucket Cloud Support

hey Norbert,

 

when reducing our pipeline to the minimum (and comparing each thing with documentation) I realize we are using 'branches' in pipelines instad of 'pull-requests'.

 

Thx for reaching out!

Norbert C Atlassian Team Feb 23, 2022

You're welcome Cristian, I'm glad to hear your issue is resolved :)

Have a good day ahead and stay safe!

Best Regards,
Norbert
Atlassian Bitbucket Cloud Support

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events