DevOps Using SpiraTeam, Jenkins and TaraVault (Parts 2-7) | Inflectra

DevOps Using SpiraTeam, Jenkins and TaraVault (Parts 2-7)

April 23rd, 2018 by inflectra

We decided it made more sense to release the entire DevOps blog as a single whitepaper, so in this paper, will be discussing some best practices and lessons learned about how to implement DevOps (Development + Operations) using the Inflectra platform in conjunction with other tools such as Jenkins. This is based on some experiences we've had internally implementing DevOps in the past 2-3 years as well as feedback and suggestions from our customers.

What are the Elements of DevOps?

There are many different ways of categorizing tools that improve DevOps, however in general it is recognized that the following seven areas need to be considered when looking for different tools that make up what is usually known as the DevOps ToolChain:

  • Plan — Plan is composed of two things: "define" and "plan". This activity refers to the business value and application requirements.
  • Package — artifact repository, application pre-deployment staging
  • Release — change management, release approvals, release automation
  • Configure — infrastructure configuration and management, Infrastructure as Code tools
  • Monitor — applications performance monitoring, end–user experience

The full whitepaper - DevOps Using SpiraTeam, Jenkins, and TaraVault, is now available - please feel free to download and share with your teams.

devops spirateam testops spiraplan jenkins continuous integration alm taravault