From the course: Agile Software Development: Remote Teams

Unlock the full course today

Join today to access over 22,400 courses taught by industry experts or purchase this course individually.

Continuous integration, delivery, and deployment

Continuous integration, delivery, and deployment

From the course: Agile Software Development: Remote Teams

Start my 1-month free trial

Continuous integration, delivery, and deployment

- [Narrator] Once your team is committed to identifying and implementing good ideas through continuous improvement, we can start looking at other continuous processes to help you deliver software faster. The next step on our continuous journey, is continuous integration, which is the practice of using smaller commits and an automated test suite to look for potential problems before code is released into production. Practices such as behavior driven development and test driven development, will create what's known as a test suite that can be run every time you want to merge code into the master branch. The test suite works like an insurance policy to guard against bugs, conflicts, and unintended consequences. There are a couple of ways to structure continuous integration. And the debate for which style is the best is always a fun one to engage in. First, developers can commit directly into master themselves. Also known as trunk-based development. With trunk-based development, it's…

Contents