How to use Git for continuous delivery

Agile development demands shorter cycles and better source control. Here's a quick primer on using Git and the Git-flow method of handling branches, commits, and merges

Become An Insider

Sign up now and get FREE access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content. Learn more.

Software delivery used to be easy. You’d write your code, team leads would add it to a build, and eventually it’d be thrown over the transom to operations, at which point you could forget about it. You might have to fix the odd bug, but it was onto the next project and the next big thing.

That’s all changed. Developers are no longer isolated from the business. They’re now part of a process that brings together everyone involved with an application’s design, development, and operation for its entire lifetime. When combined with the shift in development models, away from the age-old waterfall process to modern agile sprints, the result is a big change in the way code is delivered.

The big bang is gone. We’re now in a world where continuous integration and continuous delivery demand a change in the contents of the software engineering tool chest.

To continue reading this article register now

Notice to our Readers
We're now using social media to take your comments and feedback. Learn more about this here.