Of all the projects I’ve worked in the last few years, there’s one that stands out as my favorite: I wrote a WordPress plugin called Great Eagle (Tolkien reference) that allows my team to install and update themes and plugins from our private Bitbucket repos, via the normal wp-admin updates UI. This plugin has blasted our dev shop through the roof when it comes to development best practices, in ways we never expected or intended. It forces us to use proper version numbers because now we can’t deploy without them. It forces us to store our work in Bitbucket because now we can’t deploy without it. It forces us to use the command line en route to deploying our work (by which I simply mean, git push origin master), which then led to us using phpUnit. Now we can’t deploy unless our tests pass. We’ve arrived at the nirvana of test-driven development, all because we started with the unrelated step of deploying from git.
If this all sounds standard and obvious, great. I’d love a chance to learn from you. If this sounds like exotic rigmarole, guess what? This article is for you.
Disclaimer: My work in this plugin is heavily influenced by, and in some cases plagiarized from, the excellent GitHub
Source: https://managewp.org/articles/14230/deploying-from-bitbucket-to-wordpress
source https://williechiu40.wordpress.com/2017/01/18/deploying-from-bitbucket-to-wordpress/
No comments:
Post a Comment