Blog

Thursday, 22 June 2017

Today we will cover the "Verify" tooling from the Gartner Toolchain. Gartner defines "Verify" as follows:

Verify includes all the activities required to ensure the quality of the release. These activities can occur simultaneously with creation activities. It is important to describe specific activities designed to deliver high-quality code prior to deploying the release into production. This will include tests for both functional and nonfunctional (performance, security, usability, system environment configuration and compliance) validation. Create and verify are generally connected together via continuous integration facilities and the use of automated tools to evaluate the created components.

Source: Choosing the Right Tools for Your DevOps Toolchain, Published: 10 April 2017 ID: G00322126, Analyst(s): David Paul Williams, Thomas E. Murphy

Thursday, 15 June 2017

Written by Rene De Vleeschauwer

With our series of articles and blogs we try to help people to better understand what DevOps is all about and how to demistify it and make it understandable for all of us.

Allthough I promised last week to continue with the Gartner Toolchain, I thought it wouldn't be a bad idea to give you the link to a yearly DevOps report created by Puppet and Dora: Puppet and Dora: The 2017 Stae of DevOps report.

Thursday, 08 June 2017

Written by Rene De Vleeschauwer

In this post we will cover the "Create" step from the Gartner Toolchain, which Gartner defines Create as follows:

"Create includes all activity associated with the creation of the code release candidate, including the environment configuration. Tools here must support required platforms and fit the associated practices (e.g., behavior-driven development, code review), and may include cycles to prototype user experience (UX). This also includes source change management systems and activities around managing defects and fixes."

Source: Choosing the Right Tools for Your DevOps Toolchain, Published: 10 April 2017 ID: G00322126, Analyst(s): David Paul Williams, Thomas E. Murphy

Thursday, 01 June 2017

Written by Rene De Vleeschauwer

In the previous post I promised to talk about the "Create" step in the Gartner toolchain. But I thought an intermezzo, showing a basic DevOps toolchain for z/OS would be nice.

In our simple, yet realistic, concept whe have three types of stakeholders:

At least one person managing the issues (Jira)
Developers using Eclipse
Operations people using IKAN ALM

Thursday, 25 May 2017

Written by Rene De Vleeschauwer

This might come as a surprise, but it is amazing how very few people really understand or know what DevOps is. There have been so many occasions where I talked to people that told me their company had DevOps, while they actually just had JIRA for issue tracking or HP ALM (former HP Quality Center) for testing.

DevOps can be -and is- much more than that. Don't you agree?