Part 1b of “Using Rational Engineering Lifecycle Manager to answer hard Systems Engineering questions” blog series Preamble: Our users have been asking us for more practical examples about how to unleash the power of linked lifecycle data in Rational Engineering Lifecycle Manager (RELM), so we have decided to kick off a blog series on the […]

Part 1a of “Using Rational Engineering Lifecycle Manager to answer hard Systems Engineering questions” blog series Preamble: Our users have been asking us for more practical examples about how to unleash the power of linked lifecycle data in Rational Engineering Lifecycle Manager (RELM), so we have decided to kick off a blog series on the […]

In a recent blog post, Pete Steinfeld casually mentioned that over the past year the time to build the full Collaborative Lifecycle Management (CLM) pipeline was cut in half, but didn’t elaborate on how that reduction was accomplished.  Since I was involved with analyzing and improving the pipeline, I thought I would share, at a […]

Rational Team Concert (RTC) has started releasing quarterly. Since large features rarely fit into such short cycles, we’re making heavy use of RTC’s branching and merging functionality. That could result in merge hell, but it doesn’t. This post will give you an idea of how the RTC team uses our own source control management system, […]

This is part two in our blog series describing the transformation of our internal ALM development organization toward a Continuous Delivery model. The previous post was Walking the talk – Our journey to Continuous Delivery. In this series, we describe the motivations behind adoption of a Continuous Delivery model and the many challenges we faced as […]

You may have been reading the blog posts of my colleagues around continuous delivery including the motivation behind it, our focus areas as we transformed from annual to quarterly releases, and some process improvements that we implemented. Continuing this theme, in this blog I’ll write about one of the most dramatic changes that we underwent […]

Introduction This is the first in a series of blogs describing the transformation of our internal ALM development organization toward a Continuous Delivery model. In this series, we describe the motivations behind adoption of a Continuous Delivery model and the many challenges we faced as we embarked on this transformation from both the planning and […]

The following is in continuation of the work I described in my previous blog posting at Improving throughput in the deployment pipeline. In my earlier post, I briefly described how the IBM Jazz Collaborative Lifecycle Management (CLM) project team is developing a deployment and test execution pipeline that is allowing us to identify key product […]

Since August of 2012, we’ve been working on improving our ability to continuously deliver software. Our work was organized into four different, but overlapping areas — ways of working, continuous deployment, build, and test. The team that I work with is focused on build, the process by which we transform our source code into artifacts […]

In my previous post I described how the Collaborative Lifecycle Management (CLM) team is applying DevOps principles and practices to reach our goal of continuous delivery. When the Jazz project began in 2005, even before Rational Team Concert (RTC) existed, we maintained all our source in CVS and used hand-crafted Ant scripts, Eclipse PDE and CruiseControl […]