Every now and again we run some experiments at interconnect/it, looking at problems we’re facing, what the best practice could be, and seeing what can happen. A recent issue is that many more of our projects have multiple engineers working on them, with the result that developers can bump into one another or have integration issues both with each other but also with the third party WordPress plugins we sometimes rely upon. At the same time there’s a number of interesting ways to scale WordPress. So we decided to kill two birds with one stone. Continuous Integration (CI) is a programming method whereby developers on a team carry out regular commits to a branch and which can then be tested quickly and often within a realistic environment. There’s a simple reason for this – the longer it is since a developer wrote some code, the harder it gets for that developer to get back into it to correct the bugs. CI isn’t going to help you much if you work alone on standalone projects, but if you work in a team, or contribute with many others then it can be extremely useful.
In this article, I’ll walk you through the actual method on how to achieve continuous integration
Source: https://managewp.org/articles/13923/continuous-integration-with-wordpress
source https://williechiu40.wordpress.com/2016/11/30/continuous-integration-with-wordpress/
No comments:
Post a Comment