Automated WordPress Deployments With Bitbucket Pipelines

Tired of deploying your WordPress changes manually via FTP or SFTP? In this video, I’ll show you how to build a deployment pipeline in Bitbucket to deploy your changes automatically out to your server every time you push or merge to master.

We’ll be using Bitbucket to do this but it easily translates over to Gitlab, Github, Azure DevOps, or AWS CodePipeline. We’ll also discuss some of the built-in integrations that Bitbucket offers to not only deploy your code but to build it, inspect it, and link it with lots of different tools out there.

Hope you enjoy!

**** Join my Slack Dev Community ****

**** I write on Medium ****

**** Learn to Code Blueprint 6 month Course (FREE): Accountability | Clarity | Confidence ****

**** FREE EBOOKS ****

📰 LinkedIn ➔
📷 Instagram ➔
📱 Facebook ➔
🐦 Twitter ➔
🙋🏼‍♂️ Website ➔

#bitbucketpipelines #wordpress #devops


13 thoughts on “Automated WordPress Deployments With Bitbucket Pipelines”
  1. Hi Travis

    Our server strictly uses port 2222 & the pipeline runs on 22. Due to this I am getting the connection timeout error. How do I set port 2222 on script. Please help me out. I would highly appreciate if you could revert at the earliest. Thanks a ton in advance.

  2. Excellent! thanks for the tutorial. I've implemented and works great, now have a question. We use gulp for building SASS and JS, how can add these commands in order to compile when I push to the repo?

  3. This really helped me get an overall picture thanks. I was struggling to get all the bits working together. One thing I don't recall being mentioned here, and might have missed it, was that in my case I'd not set up any 'deployments' (Settings > deployments) so when the first pipeline ran I had an error saying "The environment 'master' in your bitbucket-pipelines.yml doesn’t match any environment defined in your settings" – I'd assumed I needed to use branch name in the 'deployment:' YAML setting becasue Travis had used 'staging' in his. Changing it to the name of one of the default deployment names in Settings > deployments fixed things. Obvious really.

  4. Perfect tutorial. followed step by step and able to deploy my laravel project first time with pipeline. Thank you. One Question: If you have fresh copy to deploy folders then only files copy and folders don't copy to server and gives "Couldn't canonicalize: No such file or directory" error. Any Idea?

  5. Can I ask a quick question, since I'm very new to CI/CD and just getting to know the workflow I'm wondering. If I make a WordPress theme using NPM packages, am I able to just place my package.json file in my repository, than run 'NPM install' and when that's finished push all the files to my server via (S)FTP? Or should I include all my files in the repository?

Leave a Reply

Your email address will not be published.

Captcha loading...