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,556,952
Community Members
 
Community Events
184
Community Groups

Defining Conditional Steps

I want to run some steps only in particular cases.

My expectation would be like:

- step:
   name: some conditional step
   script:
     - echo "run only if the condition is true"
   when: <some condition>

       

2 answers

1 accepted

0 votes
Answer accepted
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 03, 2019

Hi @Sascha Mowtschan

We don't have such configuration to set special conditions for a build to happen. 
Would you mind sharing what type of conditions you would test in the when clause?
Depending on what you share for those conditions I'll be able to open a feature request for this.

If you are attempting to avoid builds on certain commits you can use the "[skip ci]" token in their commit message. Commits with that token will not trigger builds.

Hi @Daniel Santos 

something like:

when: $(git diff --name-only --diff-filter=AMDR HEAD^ some-directory-or-file) != ""

Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 04, 2019

 

Hi @Sascha Mowtschan

I've created the following feature request for this:

Please vote on this one and add yourself as a watcher to make sure you will have any updates from that ticket. Let me know if you have more comments or questions on this matter. =]

Like Shahriar Nady likes this

awesome! thank you!

I voted and added my self as a watcher. 

Like Daniel Santos likes this
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 04, 2019

That is great, you are welcome!

- step:
          name: path1 failing step
          script:
             - echo "failing path1"
             - exit 1
          condition:
              changesets:
                 includePaths:
                   - "path1/*"
                   - "path2/*"
Like # people like this

Hi @Alex Popa

Could you please share me the documents or more configuration for this condition step?

Many thanks,

NAT

Like # people like this

At the moment, using exactly the syntax specified in the documentation results in an error that the yaml file is failing schema validation.  It says 

There is an error in your bitbucket-pipelines.yml at [pipelines > branches > master > 0 > step > condition]. 
To be precise: At least one condition is required

My step is defined as:

 - step: &codegen
name: Generate Protos
script:
- make ci_tools
- make proto_go
artifacts:
- golang/**
condition:
changesets:
includePaths:
- "proto/**/*.proto"

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events