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,466,140
Community Members
 
Community Events
176
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

Atlassian Community Events