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
# 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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.