I currently have my bitbucket-pipelines.yml file like so:
branches: # matched against branches in your Git repository
staging: # branch name
name: Get deploy sync list # files in .git-ftp-ignore should not be listed
- apt-get update
- apt-get -qq install git-ftp
- git ftp push --dry-run --user $FTP_USERNAME --passwd $FTP_PASSWORD ftp://MY_SERVER # dry run so nothing is uploaded
name: Manually deploy staging
trigger: manual # manually trigger the deployment if the sync list in the previous step looks good
- apt-get update # QUESTION: is there a way to avoid being redundant on this?
- apt-get -qq install git-ftp # QUESTION: is there a way to avoid being redundant on this?
- git ftp push --user $FTP_USERNAME --passwd $FTP_PASSWORD ftp://MY_SERVER
The first step lets me review my file change list before I deploy them. The second step lets me manually hit the deploy button if everything looks good.
My question is, is there a way to not have to re-install git-ftp in step 2? It feels redundant and a waste of build minutes to run 2 git-ftp related commands.
We’ve been building a plugin to integrate Bitbucket Server and Jenkins CI, and I’m excited to announce that our alpha is ready to download and install. It lets you seamlessly configure a Jenkins job ...
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