This website uses cookies
The web site is now storing only essential cookies on your computer. If you don't allow cookies, you may not be able to use certain features of the web site including but not limited to: log in, buy products, see personalized content, switch between site cultures. It is recommended that you allow all cookies.
800-680-1220 / +1 651-490-2860 (US) All Locations

SEARCH

The DevOps Journey at TSI, Part 1

In this 2-part series, TSI Software Engineer Jake Wardon introduces and explains the concept of DevOps, automation, and Continuous Delivery.


By Jack Wardon, TSI Software Engineer III

What is DevOps?

The DevOps Journey at TSI, Part 1DevOps, simply put, is the union of development (writing code and quality assurance) and operations (building and deploying software)—which have historically been kept apart—resulting in teams that are responsible for the entire lifecycle of a product, from development to delivery. Bringing these sides together removes many inefficiencies that would result from miscommunications over system requirements, dependencies, etc.

In order for a development team to take ownership of their operations, new processes had to be developed.  Otherwise, the time and effort required to consistently build and deploy a product would eat into a team’s development resources. Although there are many tools and processes that make small gains in efficiency, none is more synonymous with DevOps than the practice of automation.

Automation, Continuous Integration and Continuous Delivery

By automating parts of a product's lifecycle, we can ensure that the steps between development and delivery are done as consistently as possible. In addition, many of these steps can occur much more quickly—like running a regression suite, integrating code branches, or compiling and publishing software packages. 

When automation is continuously triggered by events that fit into the development lifecycle, it takes on the term “Continuous ___.” When code integration is done automatically, it is called “Continuous Integration.” When the integrated code is automatically delivered, it is called “Continuous Delivery."

The main goal of most DevOps teams is to achieve fast, consistent, and reliable delivery of their product, and Continuous Delivery is the practice that most achieves that.


Look for Part 2 of Jake's article, where he'll explore where the TSI software team is in our journey, as well as the specific tools and methods used in DevOps.

Posted on Jan 27 2021 10:25
Current rating: 0 (0 ratings)

Comments

Blog post currently doesn't have any comments.
 Security code