Setting up CI/CD with AzureDevOps Pipeline

[torelo1]

Is anyone using DevOps Pipelines for deploying new content instead of the CI/CD integration within AppService?
Currently I'm using the FTP tasks, but this doesn't feel right.
Can anyone share a pipeline? Github etc is fine as well.

[Buddhika-Kuruppu]

You usually don't need a dedicated pipeline for this 🙂

In your App Service, head to Deployment Center, connect your Azure Repos (or GitHub) source, and pick the branch you want to deploy from. From then on, any new commit to that branch will automatically update the site content — no FTP tasks needed.

One thing worth getting right up front is what you actually track in the repo. A few conventions that work well for WordPress:

• Ignore the WordPress core files — they change less often, and core upgrades can be done independently on each environment.
• Ignore wp-config.php — configuration usually differs between production and development.
• Track the wp-content/plugins and wp-content/themes folders — in most cases that's all you really need (though it's your call whether to track them at all).
• Exclude temporary/cache files, such as:
  • wp-content/advanced-cache.php
  • wp-content/object-cache.php
  • wp-content/cache/
  • wp-content/upgrades/

Microsoft's guide covers this well 👉 WordPress on Azure App Service — CI/CD

---

That said, if you want more control — build steps, approvals, multi-stage environments, etc. — a proper Azure DevOps pipeline is worth setting up.