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,293,245
Community Members
 
Community Events
165
Community Groups

Understanding and relating with Pipelines vs Deployment

I have read few documentation on deployment feature of bitbucket. But I am having hard time relating it to my current setup of pipelines deployment.

 

What I have currently is branch based deployment with pipelines. Below you will see a sample pipeline files where

 

  • Commiting on `master` branch will deploy it on staging
  • Commiting on `production` branch will deploy on production server.

 


# This is a sample build configuration for PHP.
# Check our guides at https://confluence.atlassian.com/x/e8YWN for more examples.
# Only use spaces to indent your .yml configuration.
# -----
# You can specify a custom docker image from Docker Hub as your build environment.

image: samueldebruyn/debian-git

pipelines
:
branches:
custom: # dev server
-
step:
script:
-
apt-get update
-
apt-get -qq install git-ftp
-
git ftp push -f --user $FTP_USER --passwd $FTP_PASS sftp://$SERVER_ADDRESS$DEV_PATH
production: # production server
-
step:
script:
-
apt-get update
-
apt-get -qq install git-ftp
-
git ftp push -f --user $FTP_USER --passwd $FTP_PASS sftp://$SERVER_ADDRESS$PROD_PATH

 

The current settings is working fine for me. But it doesn't uses the bitbucket deployment keyword.

 

Few things I want to get clear conception here:

 

  1. I want to use deployment feature
  2. Should I continue using the branch based deployment? Can I do "better"? Currently there is no option for rollback for me. Does bitbucket support this?
  3. I want to get input from experienced people on a flexible use of applying patches, rolling back etc.

1 comment

You can use both your branch workflow and the deployments feature!

You can just added the 'deployment' keyword to the relevant steps. So instead your configuration would look like this:

image: samueldebruyn/debian-git

pipelines
:
branches:
custom: # dev server
-
step:
deployment: test
script:
-
apt-get update
-
apt-get -qq install git-ftp
-
git ftp push -f --user $FTP_USER --passwd $FTP_PASS sftp://$SERVER_ADDRESS$DEV_PATH
production: # production server
-
step:
deployment: production
script:
-
apt-get update
-
apt-get -qq install git-ftp
-
git ftp push -f --user $FTP_USER --passwd $FTP_PASS sftp://$SERVER_ADDRESS$PROD_PATH

This will then start tracking your deployment steps on the Deployments dashboard.

Bitbucket Pipelines does not have a built in rollback feature. We have an open feature request to support this. For now you can either rerun a previous deployment pipeline (essentially rebuilding and redeploying it), or do a fix forward to revert faulty deployments.

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

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...

2,084 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you