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.
This pipeline config isn't working for PR's on the development branch. In fact pull-requests: '*' doesn't seem to work either, for what it's worth. Any thoughts?
image: node:alpine
definitions:
steps:
- step: &build
name: Build
caches:
- node
script:
- yarn
- yarn build
pipelines:
branches:
development:
- step: *build
pull-requests:
development:
- step: *build
production:
- step: *build
The YAML looks wrong to me. Perhaps the online validator can help: https://bitbucket-pipelines.prod.public.atl-paas.net/validator
No, that was just my poor formatting when pasting the yaml into the editor. (I've updated it now). Let's assume for the sake of discussion that the config is correct, which my tests have been.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, lets do this. What do you mean it does not work? Lets assume it is not running for the pull-request against develop (the PR is to be merged against develop) but the pipeline is running when you push the develop branch, correct?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.