Managing Teradata changes with RTC SCM and Jazz Build

Managing database schema changes can be a non-trivial task. Very often the danger associated with potential bad changes being deployed makes DBAs very protective of their territories and resistant to changing tried and true methods.

However, the push towards more Agile development methods, adoption of DevOps practices and Continuous Delivery capabilities is including database development in its embrace; the last 10 years or so has seen a lot of work towards aligning database development with application development best practices. That said, there are probably quite a few organisations out there where the normal practice for deploying database changes is to use some sort of “list of instructions” and various GUI DB tools with maybe some scripts thrown in. Even adopting practices such as SCM and CI can appear daunting.

Continue reading “Managing Teradata changes with RTC SCM and Jazz Build”

Managing Android platform source with RTC

My previous post on populating and testing a large Jazz repository could be tested with JMeter was primarily focused on the Work Item capability in RTC. I also needed to populate the repository with lots of SCM data and rather than take the “dumb” (ie. random) path as I had done with the Work Items, I wanted to use a more “realistic” set of artifacts.

I didn’t have to look very far: the Android platform which has apparently become the leading smart phone platform (canalys.com) and 300+ million Android-based smartphone activations (prweb.com). There are already a bunch of posts on Jim’s blog and Jazz.net on how to use RTC for Android app development, so I turned my attention to the Android Platform source, from the AOSP, which proves to be a different kettle of fish when it comes to SCM.

Continue reading “Managing Android platform source with RTC”