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,413,873
Community Members
 
Community Events
170
Community Groups

Pipline order.

Hello everyone. I have a problem with pipeline and I don't know what to do. 

If I create PR it starts CI pipeline for it, but if I commit something new before I merged PR, two new pipelines start parallel: 'commit pipeline' and 'PR pipeline'.  Problem is that I need 'PR pipeline' to start after 'commit pipeline' (it use docker image from 'commit pipeline'). Any ideas? Sorry for my English)

2 comments

Lenin Raj Atlassian Team Jan 19, 2020

Hi @Nick 

Can you please share how you have configured your pipelines? As far as I know, there should be only one pipeline running for the commits you pushed.

options:
docker: true

pipelines:
default:
- step:
name: Build
script:
- echo ${BITBUCKET_BUILD_NUMBER}
- docker login --username oauth --password $YANDEX_OAUTH cr.yandex
- docker pull cr.yandex/${YANDEX_REESTR}/${BITBUCKET_REPO_FULL_NAME,,}:latest && export CACHE_PARAM="--cache-from ${CI_REGISTRY_IMAGE}/${BITBUCKET_REPO_FULL_NAME,,}:latest" || export CACHE_PARAM=""
- docker build ${CACHE_PARAM} -t cr.yandex/${YANDEX_REESTR}/${BITBUCKET_REPO_FULL_NAME,,}:${BITBUCKET_BUILD_NUMBER} -t cr.yandex/${YANDEX_REESTR}/${BITBUCKET_REPO_FULL_NAME,,}:latest .
- docker push cr.yandex/${YANDEX_REESTR}/${BITBUCKET_REPO_FULL_NAME,,}:${BITBUCKET_BUILD_NUMBER}
- docker push cr.yandex/${YANDEX_REESTR}/${BITBUCKET_REPO_FULL_NAME,,}:latest
- step:
name: Deploy to dev
script:
- echo "Deploy to dev"
- step:
name: Rollback dev
trigger: manual
script:
- echo "Rollback dev"

pull-requests:
'**':
- step:
name: Deploy to stage
script:
- echo "Some message"
- step:
name: Deploy to stage
trigger: manual
script:
- echo "Deploy to stage"
- step:
name: Rollback stage
trigger: manual
script:
- echo "Rollback stage"

branches:
master:
- step:
name: Deploy to prod
script:
- echo "Deploy to prod"
- step:
name: Rollback prod
trigger: manual
script:
- echo "Rollback prod" 

Hi @New Yoker  That's my pipline. Two parallel piplines start with opened pull-request and new commit

Screenshot from 2020-01-19 23-49-29.png

I need to start 'pull request pipline' after 'commit pipline')) 

May be any best practices how can I change my piplines?

THX

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events