The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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)
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 @Lenin Raj Rajasekaran That's my pipline. Two parallel piplines start with opened pull-request and new commit
I need to start 'pull request pipline' after 'commit pipline'))
May be any best practices how can I change my piplines?
THX
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events