In my last post, I described how we use IBM UrbanCode Deploy to quickly and easily deploy server applications produced by each build.  In this post I will describe how we are using those deployed applications to improve our automated testing and reduce the time it takes to validate the contents of a build. Quality […]

This is the fourth installment in our blog series describing the transformation of our internal ALM development organization toward a Continuous Delivery model. The previous post was From ‘use what we sell’ to ‘practice what we preach.’ In this series, we describe the motivations behind adoption of a Continuous Delivery model and the many challenges we […]

Our journey towards IBM UrbanCode Deploy Our team has been responsible for the deployment of IBM Collaborative Lifecycle Management (CLM) on jazz.net production and staging systems since 2007.  On top of the production system known as jazz or jazz.net, we have 2 staging systems named BLUES and SOUL. We deploy to the staging system weekly, […]

In the Collaborative Lifecycle Management (CLM) project we have declared three imperatives for improvement in order to increase our agility with a goal of continuous delivery: culture, process, and tools. Of these three things, culture is, in my opinion, the most difficult thing to change because it’s less tangible than processes and tools and because culture […]

Previously I have focused on build performance in posts like Speeding up the pipeline by slowing down builds and Rethinking personal builds, but there is a lot more to a continuous delivery pipeline than build times.  Once a build produces artifacts, you need to do something with them.  Often the next step is to install […]

I have worked for IBM for about 20 years, moving back and forth between development, customer support and IT operations roles. Working in these different roles helped give me perspective for my current role as the manager for Jazz Continuous Deployments/DevOps. In this role I am responsible for ensuring that our multiple staging and self-hosting […]

“I have edited the files you wanted me to look at”, I told a team member over coffee. “I will check them in once I finish this cup.” So, after I was back, I opened the pending changes view in the Rational Team Concert Shell control panel, and began to check in the changed files. […]

“I have delivered some new files to the stream”, said a teammate at our morning scrum. “Can you please edit them?” We’re agile.  I promised to return the files within three working days. Then, I grabbed some coffee, opened Rational Team Concert Shell, and tried to remember what it was that the task bar icon […]

“It can do source control management (SCM) stuff. It is almost like the Rational Team Concert client for Eclipse IDE”, I was told, “but simpler.” “Aha! A margherita”, I thought and, being of a nature that prefers bare bones over raiments, I downloaded and installed Rational Team Concert Shell (I’m using version 4.0.2) with the […]

In my first post, I described how we were able to increase parallelism and significantly improve the end-to-end build time of the Collaborative Lifecycle Management (CLM) pipeline.  This has provided value in many ways, but as Pete Steinfeld pointed out in his Accelerating CLM builds post, it doesn’t do much to improve the developer experience.  […]