Being faster, breaking the silos, improve collaboration, etc. are not new requirements in IT, in fact they are all there for a long time. However, from time to time, we discover some ideas / methods to meet the demands, no matter how long they are playing around us. This is my view of DevOps, a kind of effort to address these challenges that can no longer be postponed.
When learning more about DevOps makes me wonder how ClearCase (CC) can contribute to this area.
Well, before we begin to look at where the CC falls on the DevOps toolchain, I think the most important thing, for interested teams, should be to think of DevOps Methodologies, and even before that, look at the DevOps values, looking to create a Culture to make, the current, teams working more closely, planning automation as a way to share faster, good code and feedbacks, at the same time to be able to control and measure what we are doing, thus avoiding misunderstanding DevOps with just a kind of tools, and then mechanically distributing bugs.
Once respected, the above, which combines with the idea of defining people, process and then the tools. We could start, without falling on the "tool-oriented approach", to see where CC can contribute to DevOps, and yes, we can see our SCM tool playing as part of the Continuous Integration / Delivery (CI / CD) practice. And there, if we think on build automation, we have good players in CC, starting with the modest, but powerful, idea of automation with triggers, which also states on its purpose, "Starting a construction or analysis of source code whenever particular objects are modified", and, in build, expanding what the "old pal" MakeFile has been doing, we have clearmake and clearaudit, doing interesting things while improving builds, sharing devired objects, creating configuration records/bill of materials, distributing or paralleling builds, and doing building avoidance for example.
CC is great, but there is no magic tool to do everything we need. This is also true in DevOps. Thus, ClearCase, and its related teams and well-qualified professionals, can benefit from many other, complementary, tools available in the market. One of them, which is in our house now, the HCL, is the UrbanCode, which certainly contributes to the CI / CD working together with ClearCase.
Ending these lines, I would like to emphasize that DevOps is, first, a challenge of "walking together," then an effort to see how your tool can contribute to it, and then see what other applications can empower you or fill in the gaps.
Author: Pedro Moura
Certified Specialist, Rational ClearCase