You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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>
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.
something like:
when: $(git diff --name-only --diff-filter=AMDR HEAD^ some-directory-or-file) != ""
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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. =]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is great, you are welcome!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- step: name: path1 failing step script: - echo "failing path1" - exit 1 condition: changesets: includePaths: - "path1/*" - "path2/*"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alex Popa
Could you please share me the documents or more configuration for this condition step?
Many thanks,
NAT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@NAT search for "condition", because BB pipeline documentation sucks https://support.atlassian.com/bitbucket-cloud/docs/configure-bitbucket-pipelinesyml/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.